Re: Next development steps?

I believe I can find some time to hang around here.

Regards,
Siva Kumar.K

-----Original Message-----
From: Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz]
Sent: Wednesday, December 14, 2005 10:34 PM
To: Dave Page
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] Next development steps?

> > 1) clean the code (and UI) with drop all non-trivial features
> > - these features make the code unreadable and complicated with
> > no proper behaviour right now
> > - there is no error report for them since libpq support
> > (exclude [#1000413] Optimistic lock cannot be used with
> > updateable
> > cursors - I think updateable cursor doesn't work at all)
>
> What features do you have in mind?

All which use backend_tuples or is unreachable at least.
I'm sorry I don't have a list. It is only my ideas based on
what I see through patching. I also try to start cleaning code
and I always stop becouse I go to updateable cursor implementation
or DRIVER_CURSOR or something similar.

> I'm more inclined to create a stable branch and develop in tip.

I'm sorry I'm unable to translate "develop in tip".
I think that we use current stable version as start point for
development branch. I don't think we could share code between this
two branches. It doesn't lead to better (readable) code.

> Can I also assume you expect to be around for a good while to work on
> this ambitious plan? ODBC developers are few and far between, so
> starting a major project can be quite a commitment for all of us.

Yes. I'm planning this mainly for me (maybe someone join me/us).

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly

**********************************************************

The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email

************************************************************