pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedNEW ODBC DRIVER
18+ messages / 8 participants
[nested] [flat]
* NEW ODBC DRIVER
@ 1998-05-08 16:35 Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 2 replies; 18+ messages in thread
From: Byron Nikolaidis @ 1998-05-08 16:35 UTC (permalink / raw)
To: pgsql-interfaces; +Cc: Benoit Foucher <bfoucher@pratique.fr>; Stephen Davies <scldad@sdc.com.au>; Jose' Soares Da Silva <sferac@bo.nettuno.it>; Hannu Krosing <hannu@trust.ee>; Tom Ivar Helbekkmo <tih+mail@Hamartun.Priv.NO>; Sbragion Denis <infotecn@tin.it>; Dario Fumagalli <dfumagalli@art-media.it>; Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>; Paul Lisewski <paull@techone.com.au>; Christopher Luk <wluk@hkcccc.org>; Aleksey Demakov <avd@avd.garsib.ru>; Tony Cowderoy <tony@nthfen.demon.co.uk>
Hello all,
There is a new odbc driver (version 6.30.0237) and source code at our
website (http://www.insightdist.com/psqlodbc). This one contains some
bug fixes AND alot of setup options! You can now configure the driver
more closely to match your needs hopefully. Please click on the version
link and/or the "dialog boxes" link for more detailed information. Some
quick highlights are:
- By democratic vote, uses ISO datestyle, period! Automatically sets
this datestyle to backend on connection.
- Advanced options for Driver and Datasource (and lots of them).
- Ability to control whether cursors are used, thus emulating the old
driver/libpq behavior.
- Ability to control how unknown sizes are reported: "Longest" emulates
old driver/libpq behavior.
- Recognizing Unique indexes is a driver option.
- Some data type mappings and data type sizes are configurable.
- SQLExtendedFetch implemented when not using cursors.
There is also a "Defaults" button to set all these options back to
optimum settings.
Note, there are performance issues involved with not using cursors,
since the driver must suck down all the rows in the result set.
However, there are some advantages when it comes to updating tables
since the tables are not kept locked by the backend. If you are having
problems with locked tables or the driver hanging, try setting Use
Cursors to false. This is a workaround until whenever the backend
locking improves. Also, when not using cursors, the sizes of character
data types varchar and text can be known since all the tuples are
retrieved in the result set. So if you set the option "Longest" on the
Advanced Options (Driver), this will be possible.
Feedback on this new driver is appreciated.
Regards,
Byron.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] NEW ODBC DRIVER
@ 1998-05-08 17:49 Chris Osborn <fozztexx@talia.hq.vxn.com>
parent: Byron Nikolaidis <byronn@insightdist.com>
1 sibling, 2 replies; 18+ messages in thread
From: Chris Osborn @ 1998-05-08 17:49 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
I just downloaded it, and I cannot get any queries that have an
"ORDER BY" in them to work. Access '97 keeps returning an ODBC call
failed error, and gives me the message:
ERROR: The field being ordered must appear in the target list (#1)
If I cut and paste the SQL code directly into a psql session, it
runs just fine.
---
Chris Osborn, Network Administrator T3West/WebCow!
707 255 9330 x225 - Voice 1804 Soscol Ave, #203
707 224 9916 - Fax Napa, CA 94559
<fozztexx@t3west.com> <http://t3west.com/;
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] NEW ODBC DRIVER
@ 1998-05-08 18:12 Chris Osborn <fozztexx@talia.hq.vxn.com>
parent: Chris Osborn <fozztexx@talia.hq.vxn.com>
1 sibling, 1 reply; 18+ messages in thread
From: Chris Osborn @ 1998-05-08 18:12 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
It also keeps insisting that the connection is read only, even
though I unchecked the read only boxes in both the Driver settings
and Advanced settings.
---
Chris Osborn, Network Administrator T3West/WebCow!
707 255 9330 x225 - Voice 1804 Soscol Ave, #203
707 224 9916 - Fax Napa, CA 94559
<fozztexx@t3west.com> <http://t3west.com/;
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] NEW ODBC DRIVER
@ 1998-05-10 00:12 Byron Nikolaidis <byronn@insightdist.com>
parent: Chris Osborn <fozztexx@talia.hq.vxn.com>
1 sibling, 1 reply; 18+ messages in thread
From: Byron Nikolaidis @ 1998-05-10 00:12 UTC (permalink / raw)
To: Chris Osborn <fozztexx@talia.hq.vxn.com>; +Cc: pgsql-interfaces
Access insists on using order by clauses like that, even though the
driver returns information saying it can't support it!
Postgres simply can't handle order by clauses without the fields also
being in the target.
The error you see is a legitimate error coming from the backend.
When the backend can handle those kinds of order by clauses, the error
will stop happening.
Byron
Chris Osborn wrote:
> I just downloaded it, and I cannot get any queries that have an
> "ORDER BY" in them to work. Access '97 keeps returning an ODBC call
> failed error, and gives me the message:
>
> ERROR: The field being ordered must appear in the target list (#1)
>
> If I cut and paste the SQL code directly into a psql session, it
> runs just fine.
>
> ---
> Chris Osborn, Network Administrator T3West/WebCow!
> 707 255 9330 x225 - Voice 1804 Soscol Ave, #203
> 707 224 9916 - Fax Napa, CA 94559
> <fozztexx@t3west.com> <http://t3west.com/;
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] NEW ODBC DRIVER
@ 1998-05-10 00:15 Byron Nikolaidis <byronn@insightdist.com>
parent: Chris Osborn <fozztexx@talia.hq.vxn.com>
0 siblings, 0 replies; 18+ messages in thread
From: Byron Nikolaidis @ 1998-05-10 00:15 UTC (permalink / raw)
To: Chris Osborn <fozztexx@talia.hq.vxn.com>; +Cc: pgsql-interfaces
Hello,
For Access to be able to update records it must have a unique key.
Access 95 and 97 can ask for the key if the driver doesn't automatically
return it.
Access 2.0 can not ask and relies completely on the driver to return the
unique key.
There is a setting in the Driver Options dialog which controls how this
happens.
It is called "Recognize Unique Indexes". If checked, the driver will
automatically return the information. If not checked (the default), it
will not return a unique index.
Hope this helps.
Byron
Chris Osborn wrote:
> It also keeps insisting that the connection is read only, even
> though I unchecked the read only boxes in both the Driver settings
> and Advanced settings.
>
> ---
> Chris Osborn, Network Administrator T3West/WebCow!
> 707 255 9330 x225 - Voice 1804 Soscol Ave, #203
> 707 224 9916 - Fax Napa, CA 94559
> <fozztexx@t3west.com> <http://t3west.com/;
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] NEW ODBC DRIVER
@ 1998-05-11 10:45 Chris Osborn <fozztexx@talia.hq.vxn.com>
parent: Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 18+ messages in thread
From: Chris Osborn @ 1998-05-11 10:45 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
So what can I do to sort in Access '97? I doubt the backend will
be getting changed anytime soon.
---
Chris Osborn, Network Administrator T3West/WebCow!
707 255 9330 x225 - Voice 1804 Soscol Ave, #203
707 224 9916 - Fax Napa, CA 94559
<fozztexx@t3west.com> <http://t3west.com/;
On May. 09 98, 17:12 PDT, "Byron Nikolaidis" <byronn@insightdist.com>
wrote:
> Access insists on using order by clauses like that, even though
> the driver returns information saying it can't support it!
> Postgres simply can't handle order by clauses without the fields
> also being in the target.
> The error you see is a legitimate error coming from the backend.
> When the backend can handle those kinds of order by clauses, the
> error will stop happening.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: NEW ODBC DRIVER
@ 1998-05-11 12:35 Byron Nikolaidis <byronn@insightdist.com>
parent: Jose' Soares Da Silva <sferac@bo.nettuno.it>
1 sibling, 1 reply; 18+ messages in thread
From: Byron Nikolaidis @ 1998-05-11 12:35 UTC (permalink / raw)
To: Jose' Soares Da Silva <sferac@bo.nettuno.it>; +Cc: pgsql-interfaces
Jose' Soares Da Silva wrote:
> I have a problem with types.
> I created a table with a column of type money and another with type
> bool, Access translate money to numeric (double precision) and bool to
> text.
> I thought that Access recognized this types as Money and Yes/No.
> Is it an ODBC or a PostgreSQL problem ?
> Thanks, Jose'
In my tests, Access never bothered to retrieve the information returned by
the driver which says that the field is a MONEY type. I chose to make it a
numeric, but I could make it character, which would allow you to see the
money symbols, but I'm not sure if you could perform calculations on it?
As for the BOOL problem, I tried to return it as a SQL_BOOL, but Access
displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE translate to a -1, I
have no idea. But for that reason, I chose to make it a character type
instead.
I could add options to the setup dialog for handling these two types, if
anyone's interested.
Byron
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: NEW ODBC DRIVER
@ 1998-05-11 13:25 Jose' Soares Da Silva <sferac@bo.nettuno.it>
parent: Byron Nikolaidis <byronn@insightdist.com>
1 sibling, 2 replies; 18+ messages in thread
From: Jose' Soares Da Silva @ 1998-05-11 13:25 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
On Fri, 8 May 1998, Byron Nikolaidis wrote:
> Hello all,
>
> There is a new odbc driver (version 6.30.0237) and source code at our
> ...
> Feedback on this new driver is appreciated.
>
I just down load the ODBC 6.30.0238
and seems that it works well with Access. Thanks to Byron. Great job!
I have a problem with types.
I created a table with a column of type money and another with type
bool, Access translate money to numeric (double precision) and bool to
text.
I thought that Access recognized this types as Money and Yes/No.
Is it an ODBC or a PostgreSQL problem ?
Thanks, Jose'
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-11 16:15 Sbragion Denis <infotecn@tin.it>
parent: Jose' Soares Da Silva <sferac@bo.nettuno.it>
1 sibling, 1 reply; 18+ messages in thread
From: Sbragion Denis @ 1998-05-11 16:15 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; Jose' Soares Da Silva <sferac@bo.nettuno.it>; +Cc: pgsql-interfaces
Hello,
At 08.35 11/05/98 -0400, Byron Nikolaidis wrote:
>As for the BOOL problem, I tried to return it as a SQL_BOOL, but Access
>displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE translate to a -1, I
>have no idea. But for that reason, I chose to make it a character type
>instead.
This is an MS brain damage implementation of Booleans. It is used this way
starting from MS Access 1.0 up to VB 5.0. I don't know why MS decided to
use this convention in the early MS Access 1.0 age but for compatibility
reason they had to retain it up to the most recent version of their
development programs.
Bye !
Dr. Sbragion Denis
InfoTecna
Tel, Fax: +39 39 2324054
URL: http://space.tin.it/internet/dsbragio
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-11 17:07 Jackson, DeJuan <djackson@cpsgroup.com>
0 siblings, 0 replies; 18+ messages in thread
From: Jackson, DeJuan @ 1998-05-11 17:07 UTC (permalink / raw)
To: Sbragion Denis <infotecn@tin.it>; Byron Nikolaidis <byronn@insightdist.com>; Jose' Soares Da Silva <sferac@bo.nettuno.it>; +Cc: pgsql-interfaces
One word 'BASIC'.
-DEJ
> -----Original Message-----
> From: Sbragion Denis [SMTP:infotecn@tin.it]
> Sent: Monday, May 11, 1998 11:15 AM
> To: Byron Nikolaidis; Jose' Soares Da Silva
> Cc: interfaces postgres
> Subject: Re: [INTERFACES] Re: NEW ODBC DRIVER
>
> Hello,
>
> At 08.35 11/05/98 -0400, Byron Nikolaidis wrote:
> >As for the BOOL problem, I tried to return it as a SQL_BOOL, but
> Access
> >displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE translate to a
> -1, I
> >have no idea. But for that reason, I chose to make it a character
> type
> >instead.
>
> This is an MS brain damage implementation of Booleans. It is used this
> way
> starting from MS Access 1.0 up to VB 5.0. I don't know why MS decided
> to
> use this convention in the early MS Access 1.0 age but for
> compatibility
> reason they had to retain it up to the most recent version of their
> development programs.
>
> Bye !
>
> Dr. Sbragion Denis
> InfoTecna
> Tel, Fax: +39 39 2324054
> URL: http://space.tin.it/internet/dsbragio
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-11 18:42 Byron Nikolaidis <byronn@insightdist.com>
parent: Sbragion Denis <infotecn@tin.it>
0 siblings, 1 reply; 18+ messages in thread
From: Byron Nikolaidis @ 1998-05-11 18:42 UTC (permalink / raw)
To: Sbragion Denis <infotecn@tin.it>; +Cc: Jose' Soares Da Silva <sferac@bo.nettuno.it>; pgsql-interfaces; Jackson, DeJuan <djackson@cpsgroup.com>; Hannu Krosing <hannu@trust.ee>
Sbragion Denis wrote:
> Hello,
>
> At 08.35 11/05/98 -0400, Byron Nikolaidis wrote:
> >As for the BOOL problem, I tried to return it as a SQL_BOOL, but Access
> >displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE translate to a -1, I
> >have no idea. But for that reason, I chose to make it a character type
> >instead.
>
> This is an MS brain damage implementation of Booleans. It is used this way
> starting from MS Access 1.0 up to VB 5.0. I don't know why MS decided to
> use this convention in the early MS Access 1.0 age but for compatibility
> reason they had to retain it up to the most recent version of their
> development programs.
>
>
OK,
I'm gonna make it an option. But, as I mentioned before, there are some
weirdnesses with Access. Here's another weird thing with the way it handles
NULL SQL_BIT columns.
If I have my Postgres bool column, and it contains a NULL, Access automatically
displays it as "0". Then if I try to update the record, it uses the "0" in the
where clause. Well guess what, no records are updated because the "0" doesn't
match the NULL in the record, and you get this ugly message about a user
conflict!
When BOOLS are handled as character data, this doesnt happen of course.
Anybody got any ideas about this?
Byron
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-11 19:33 Felix Morley Finch <felix@crowfix.com>
0 siblings, 0 replies; 18+ messages in thread
From: Felix Morley Finch @ 1998-05-11 19:33 UTC (permalink / raw)
To: pgsql-interfaces
(I can't follow the original attributions)
>> As for the BOOL problem, I tried to return it as a SQL_BOOL, but
>> Access displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE
>> translate to a -1, I have no idea. But for that reason, I chose to
>> make it a character type instead.
> This is an MS brain damage implementation of Booleans. It is used
> this way starting from MS Access 1.0 up to VB 5.0. I don't know why
> MS decided to use this convention in the early MS Access 1.0 age but
> for compatibility reason they had to retain it up to the most recent
> version of their development programs.
I bet it's because -1 is all bits on. Still brain damaged.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
PGP = 91 B3 94 7C E9 E8 76 2D E1 63 51 AA A0 48 89 2F ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
^ permalink raw reply [nested|flat] 18+ messages in thread
* RE: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-11 19:44 Jackson, DeJuan <djackson@cpsgroup.com>
0 siblings, 0 replies; 18+ messages in thread
From: Jackson, DeJuan @ 1998-05-11 19:44 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; Sbragion Denis <infotecn@tin.it>; +Cc: Jose' Soares Da Silva <sferac@bo.nettuno.it>; pgsql-interfaces; Jackson, DeJuan <djackson@cpsgroup.com>; Hannu Krosing <hannu@trust.ee>
No fixes here, but what it sounds like is that Access is using it's own
BOOL type to represent the BOOL in PostgreSQL. Access' BOOL type can't
be null, it can only be true or false, y or n, -1 or 0 depending on how
you want it displayed. So, it's translating NULL's into it's default of
false.
-DEJ
> -----Original Message-----
> From: Byron Nikolaidis [SMTP:byronn@insightdist.com]
> Sent: Monday, May 11, 1998 1:42 PM
> To: Sbragion Denis
> Cc: Jose' Soares Da Silva; interfaces postgres; Jackson, DeJuan;
> Hannu Krosing
> Subject: Re: [INTERFACES] Re: NEW ODBC DRIVER
>
> Sbragion Denis wrote:
>
> > Hello,
> >
> > At 08.35 11/05/98 -0400, Byron Nikolaidis wrote:
> > >As for the BOOL problem, I tried to return it as a SQL_BOOL, but
> Access
> > >displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE translate to
> a -1, I
> > >have no idea. But for that reason, I chose to make it a character
> type
> > >instead.
> >
> > This is an MS brain damage implementation of Booleans. It is used
> this way
> > starting from MS Access 1.0 up to VB 5.0. I don't know why MS
> decided to
> > use this convention in the early MS Access 1.0 age but for
> compatibility
> > reason they had to retain it up to the most recent version of their
> > development programs.
> >
> >
>
> OK,
>
> I'm gonna make it an option. But, as I mentioned before, there are
> some
> weirdnesses with Access. Here's another weird thing with the way it
> handles
> NULL SQL_BIT columns.
>
> If I have my Postgres bool column, and it contains a NULL, Access
> automatically
> displays it as "0". Then if I try to update the record, it uses the
> "0" in the
> where clause. Well guess what, no records are updated because the "0"
> doesn't
> match the NULL in the record, and you get this ugly message about a
> user
> conflict!
>
> When BOOLS are handled as character data, this doesnt happen of
> course.
>
> Anybody got any ideas about this?
>
> Byron
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: NEW ODBC DRIVER
@ 1998-05-12 08:50 Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>
parent: Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 0 replies; 18+ messages in thread
From: Olaf Mittelstaedt @ 1998-05-12 08:50 UTC (permalink / raw)
To: pgsql-interfaces
> > At 08.35 11/05/98 -0400, Byron Nikolaidis wrote:
> > >As for the BOOL problem, I tried to return it as a SQL_BOOL, but Access
> > >displayed it as 0=FALSE, and (-1)=TRUE. Why does TRUE translate to a -1, I
> > >have no idea. But for that reason, I chose to make it a character type
> > >instead.
> >
>
> If I have my Postgres bool column, and it contains a NULL, Access automatically
> displays it as "0". Then if I try to update the record, it uses the "0" in the
> where clause. Well guess what, no records are updated because the "0" doesn't
> match the NULL in the record, and you get this ugly message about a user
> conflict!
>
> When BOOLS are handled as character data, this doesnt happen of course.
>
> Anybody got any ideas about this?
When migrating tables from Access 2.0 to an SQL Server (Informix,
Interbase or PostgreSQL) I'm using INT4 to simulate boolean values
(0=False, -1=True), all Access queries using boolean columns will
work as before with native Access tables:
"... WHERE (b=True);" selects all rows with column b == -1
"... WHERE (b=False);" selects all rows with column b == 0
"... WHERE (b is Null);" selects all rows with column b == NULL
Of course you can't issue queries like "...where (b = true);" on the
UNIX side.
Regards,
Olaf
--
Olaf Mittelstaedt - IuK - mittelstaedt@fh-ulm.de
Fachhochschule Ulm Prittwitzstr. 10 89075 Ulm
Tel.: +49 (0)731-502-8220 Fax: -8270
Tertium non datur.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-12 11:02 Jose' Soares Da Silva <sferac@bo.nettuno.it>
parent: Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 2 replies; 18+ messages in thread
From: Jose' Soares Da Silva @ 1998-05-12 11:02 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
On Mon, 11 May 1998, Byron Nikolaidis wrote:
>
>
> Jose' Soares Da Silva wrote:
>
> > I have a problem with types.
> > I created a table with a column of type money and another with type
> > bool, Access translate money to numeric (double precision) and bool to
> > text.
> > I thought that Access recognized this types as Money and Yes/No.
> > Is it an ODBC or a PostgreSQL problem ?
> > Thanks, Jose'
>
>
> In my tests, Access never bothered to retrieve the information returned by
> the driver which says that the field is a MONEY type. I chose to make it a
> numeric, but I could make it character, which would allow you to see the
> money symbols, but I'm not sure if you could perform calculations on it?
Numeric should be OK, but Access doesn't read the data on money fields.
Access displays the word "#deleted" on the field instead of data.
Jose'
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-12 12:17 Jose' Soares Da Silva <sferac@bo.nettuno.it>
parent: Jose' Soares Da Silva <sferac@bo.nettuno.it>
1 sibling, 0 replies; 18+ messages in thread
From: Jose' Soares Da Silva @ 1998-05-12 12:17 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
On Tue, 12 May 1998, Jose' Soares Da Silva wrote:
> On Mon, 11 May 1998, Byron Nikolaidis wrote:
>
> >
> > In my tests, Access never bothered to retrieve the information returned by
> > the driver which says that the field is a MONEY type. I chose to make it a
> > numeric, but I could make it character, which would allow you to see the
> > money symbols, but I'm not sure if you could perform calculations on it?
>
> Numeric should be OK, but Access doesn't read the data on money fields.
> Access displays the word "#deleted" on the field instead of data.
Please forget the above message, now it works. The reason for "#deleted"
probably was that Access put this field as the primary key.
Jose'
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: [INTERFACES] Re: NEW ODBC DRIVER
@ 1998-05-12 14:37 Byron Nikolaidis <byronn@insightdist.com>
parent: Jose' Soares Da Silva <sferac@bo.nettuno.it>
1 sibling, 0 replies; 18+ messages in thread
From: Byron Nikolaidis @ 1998-05-12 14:37 UTC (permalink / raw)
To: Jose' Soares Da Silva <sferac@bo.nettuno.it>; +Cc: pgsql-interfaces
This sounds like a different problem. I have tested money columns and at least I
can see the data. Since the driver must convert the money type into a numeric,
maybe it is having trouble with your type of money. Didn't you say that you are
not using dollars?
Byron
Jose' Soares Da Silva wrote:
> On Mon, 11 May 1998, Byron Nikolaidis wrote:
>
> >
> >
> > Jose' Soares Da Silva wrote:
> >
> > > I have a problem with types.
> > > I created a table with a column of type money and another with type
> > > bool, Access translate money to numeric (double precision) and bool to
> > > text.
> > > I thought that Access recognized this types as Money and Yes/No.
> > > Is it an ODBC or a PostgreSQL problem ?
> > > Thanks, Jose'
> >
> >
> > In my tests, Access never bothered to retrieve the information returned by
> > the driver which says that the field is a MONEY type. I chose to make it a
> > numeric, but I could make it character, which would allow you to see the
> > money symbols, but I'm not sure if you could perform calculations on it?
>
> Numeric should be OK, but Access doesn't read the data on money fields.
> Access displays the word "#deleted" on the field instead of data.
>
> Jose'
^ permalink raw reply [nested|flat] 18+ messages in thread
* New odbc driver
@ 2000-04-02 20:03 Byron Nikolaidis <byron.nikolaidis@home.com>
0 siblings, 0 replies; 18+ messages in thread
From: Byron Nikolaidis @ 2000-04-02 20:03 UTC (permalink / raw)
To: pgsql-interfaces
The new driver that Thomas and Tom fixed is now available for windows.
ftp://ftp.postgresql.org/pub/odbc/index.html
Byron
^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2000-04-02 20:03 UTC | newest]
Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-05-08 16:35 NEW ODBC DRIVER Byron Nikolaidis <byronn@insightdist.com>
1998-05-08 17:49 ` Chris Osborn <fozztexx@talia.hq.vxn.com>
1998-05-08 18:12 ` Chris Osborn <fozztexx@talia.hq.vxn.com>
1998-05-10 00:15 ` Byron Nikolaidis <byronn@insightdist.com>
1998-05-10 00:12 ` Byron Nikolaidis <byronn@insightdist.com>
1998-05-11 10:45 ` Chris Osborn <fozztexx@talia.hq.vxn.com>
1998-05-11 13:25 ` Jose' Soares Da Silva <sferac@bo.nettuno.it>
1998-05-11 12:35 ` Byron Nikolaidis <byronn@insightdist.com>
1998-05-12 11:02 ` Jose' Soares Da Silva <sferac@bo.nettuno.it>
1998-05-12 12:17 ` Jose' Soares Da Silva <sferac@bo.nettuno.it>
1998-05-12 14:37 ` Byron Nikolaidis <byronn@insightdist.com>
1998-05-11 16:15 ` Sbragion Denis <infotecn@tin.it>
1998-05-11 18:42 ` Byron Nikolaidis <byronn@insightdist.com>
1998-05-12 08:50 ` Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>
1998-05-11 17:07 RE: [INTERFACES] Re: NEW ODBC DRIVER Jackson, DeJuan <djackson@cpsgroup.com>
1998-05-11 19:33 RE: [INTERFACES] Re: NEW ODBC DRIVER Felix Morley Finch <felix@crowfix.com>
1998-05-11 19:44 RE: [INTERFACES] Re: NEW ODBC DRIVER Jackson, DeJuan <djackson@cpsgroup.com>
2000-04-02 20:03 New odbc driver Byron Nikolaidis <byron.nikolaidis@home.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox