ell
- Original Message -
From: "Kevin Grittner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
Sent: Monday, August 01, 2005 12:31 PM
Subject: Re: [BUGS] problem odbc 8.0 with EOModeler
It looks like this is being treated on the server as t
? (i don't need to add additional quotes for
other odbc data sources)
When query against numerical columns, things works quite well
- Original Message -
From: "Kevin Grittner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
Sent: Monday,
s for
other odbc data sources)
When query against numerical columns, things works quite well
- Original Message -
From: "Kevin Grittner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
Sent: Monday, August 01, 2005 12:31 PM
Subject: Re: [BUGS] probl
really indicate that EOModeler and postgresql-odbc can not communicate
correctly. in other words, postgresql-odbc has special API's that not make
sense to
EOModeler.
----- Original Message -
From: "Kevin Grittner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
Sent: Monday, A
ot make
sense to
EOModeler.
- Original Message -
From: "Kevin Grittner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
Sent: Monday, August 01, 2005 8:25 AM
Subject: Re: [BUGS] problem odbc 8.0 with EOModeler
Is the column name "Elim" or "elim"? If
Is the column name "Elim" or "elim"? If the former, try putting quotes around
it, as required by the ANSI and ISO standards for mixed case identifiers. Some
database products fail to comply with the standards in this respect.
PostgreSQL comes close, although it treats unquoted identifers as a
