Thread: ODBC release plans?
With the server release around the corner, should we aim for a release of the ODBC driver as well? What are the open issues? -- Peter Eisentraut http://developer.postgresql.org/~petere/
Peter Eisentraut wrote: > With the server release around the corner, should we aim for a release > of the ODBC driver as well? What are the open issues? Conversion problem with unicode, see my message from Jan 4th. I also have a numeric problem, which I'll have to trace down the next days. Regards, Andreas
> -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Peter Eisentraut > Sent: 16 January 2005 08:26 > To: pgsql-odbc@postgresql.org > Subject: [ODBC] ODBC release plans? > > With the server release around the corner, should we aim for > a release > of the ODBC driver as well? What are the open issues? Open issues are on Gborg, though the majority haven't been verified as actual bugs. My workload is high at the moment, so I do not intend to try to do a new release right now (maybe in a week or two?). The Win32 installer will be and has been shipping with 08.00.0003 which is essentially the same as .0002 (the last snapshot release) bar a minor fix from Scot. Judging from the lack of bug reports I've seen on it, it's pretty stable. Regards, Dave.
Hi all, I have run into a problem with release 8 that isn't showing up when I switch back to 7: http://archives.postgresql.org/pgsql-odbc/2004-12/msg00055.php Regards, George ----- Original Message ----- From: "Dave Page" <dpage@vale-housing.co.uk> To: "Peter Eisentraut" <peter_e@gmx.net>; <pgsql-odbc@postgresql.org> Sent: Sunday, January 16, 2005 6:16 AM Subject: Re: [ODBC] ODBC release plans? > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Peter Eisentraut > Sent: 16 January 2005 08:26 > To: pgsql-odbc@postgresql.org > Subject: [ODBC] ODBC release plans? > > With the server release around the corner, should we aim for > a release > of the ODBC driver as well? What are the open issues? Open issues are on Gborg, though the majority haven't been verified as actual bugs. My workload is high at the moment, so I do not intend to try to do a new release right now (maybe in a week or two?). The Win32 installer will be and has been shipping with 08.00.0003 which is essentially the same as .0002 (the last snapshot release) bar a minor fix from Scot. Judging from the lack of bug reports I've seen on it, it's pretty stable. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
I had the following problem which I have not been able to run down ? I use the ODBC driver for my c++ client, when I change the underlying column from a character varying(400) to Text. The client now sees this as a memo field. Is there something in the ODBC driver that makes this assumption ? Jim ----- Original Message ----- From: "George Weaver" <gweaver@shaw.ca> To: "Dave Page" <dpage@vale-housing.co.uk>; "Peter Eisentraut" <peter_e@gmx.net>; <pgsql-odbc@postgresql.org> Sent: Sunday, January 16, 2005 8:03 AM Subject: Re: [ODBC] ODBC release plans? > Hi all, > > I have run into a problem with release 8 that isn't showing up when I > switch back to 7: > > http://archives.postgresql.org/pgsql-odbc/2004-12/msg00055.php > > Regards, > George > > ----- Original Message ----- > From: "Dave Page" <dpage@vale-housing.co.uk> > To: "Peter Eisentraut" <peter_e@gmx.net>; <pgsql-odbc@postgresql.org> > Sent: Sunday, January 16, 2005 6:16 AM > Subject: Re: [ODBC] ODBC release plans? > > > > >> -----Original Message----- >> From: pgsql-odbc-owner@postgresql.org >> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Peter Eisentraut >> Sent: 16 January 2005 08:26 >> To: pgsql-odbc@postgresql.org >> Subject: [ODBC] ODBC release plans? >> >> With the server release around the corner, should we aim for >> a release >> of the ODBC driver as well? What are the open issues? > > Open issues are on Gborg, though the majority haven't been verified as > actual bugs. > > My workload is high at the moment, so I do not intend to try to do a new > release right now (maybe in a week or two?). The Win32 installer will be > and has been shipping with 08.00.0003 which is essentially the same as > .0002 (the last snapshot release) bar a minor fix from Scot. Judging > from the lack of bug reports I've seen on it, it's pretty stable. > > Regards, Dave. > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) >
> I had the following problem which I have not been able to run down ? > > I use the ODBC driver for my c++ client, when I change the underlying > column > from a character varying(400) to Text. The > client now sees this as a memo field. Is there something in the ODBC > driver > that makes this assumption ? By C++ client, do you mean Borland C++ Builder? The IDE defaults the field types based on internal assumptions. You can override them, but it's a pain. Let me know if you are still stuck and maybe I can give you some tips. Merlin
Merlin, Yes Borland C++ builder is exactly what I am using .... Jim ----- Original Message ----- From: "Merlin Moncure" <merlin.moncure@rcsonline.com> To: "James M Doherty PGADMIN" <jimmyd@jdoherty.net> Cc: <pgsql-odbc@postgresql.org> Sent: Monday, January 17, 2005 8:32 AM Subject: RE: [ODBC] ODBC release plans? > I had the following problem which I have not been able to run down ? > > I use the ODBC driver for my c++ client, when I change the underlying > column > from a character varying(400) to Text. The > client now sees this as a memo field. Is there something in the ODBC > driver > that makes this assumption ? By C++ client, do you mean Borland C++ Builder? The IDE defaults the field types based on internal assumptions. You can override them, but it's a pain. Let me know if you are still stuck and maybe I can give you some tips. Merlin
> Merlin, > > Yes Borland C++ builder is exactly what I am using .... > > Jim Well, since a text field is unbounded, the VCL is going to give you a TMemoField which is really what is supposed to happen, TMemoField being designed to handle unbounded fields. By the way, this is not a problem with the ODBC driver. So, I'd suggest the following alternatives: 1. Learn to live with TMemoField. This basically you means you need to pick up some 3rd party VCL controls, especially a grid replacement, one that doesn't say 'memo' for TMemoField. The build it edit control for memo fields TDBMemo, is ok, but there are better ones out there. 2. Cast your field expression coming in and going out, now it gets treated as a string field (rebind your fields to the dataset). Of course, I gather that kind of goes against the whole reason for going with the 'text' type to begin with. Merlin p.s. If you are doing serious development in C++ builder, I strongly recommend looking at the Zeos database components. They are very fast and access the database directly without going through the BDE. (or ODBC). http://www.zeoslib.net
We use BCB and Delphi with direct access (libpq 73) via Zeoslib since 3 months. Seen results and performance, throwed away the PG odbc. Zeos (6.1.5) does not shine for ADO access, but all the wrappers around native interfaces work really well. Regards Claudio Duffini ""Merlin Moncure"" <merlin.moncure@rcsonline.com> ha scritto nel messaggio news:6EE64EF3AB31D5448D0007DD34EEB3412A75BB@Herge.rcsinc.local... > > Merlin, > > > > Yes Borland C++ builder is exactly what I am using .... > > > > Jim > > Well, since a text field is unbounded, the VCL is going to give you a > TMemoField which is really what is supposed to happen, TMemoField being > designed to handle unbounded fields. By the way, this is not a problem > with the ODBC driver. > > > So, I'd suggest the following alternatives: > 1. Learn to live with TMemoField. This basically you means you need to > pick up some 3rd party VCL controls, especially a grid replacement, one > that doesn't say 'memo' for TMemoField. The build it edit control for > memo fields TDBMemo, is ok, but there are better ones out there. > > 2. Cast your field expression coming in and going out, now it gets > treated as a string field (rebind your fields to the dataset). Of > course, I gather that kind of goes against the whole reason for going > with the 'text' type to begin with. > > Merlin > p.s. If you are doing serious development in C++ builder, I strongly > recommend looking at the Zeos database components. They are very fast > and access the database directly without going through the BDE. (or > ODBC). > > http://www.zeoslib.net > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org >