Comparing Enumerated Types between JDBC and ODBC drivers

While testing the waters of porting a MS-Access application to OObase.
I noticed that certain types such as Enumerated types - as well as
other types (i.e. interval), where not representable in OObase using
the JDBC driver. However, when I used the ODBC driver for OOBase all
such types were once again representable (they were represented as
text).

Is this an issues with OOBase or an issue with the representation of
complex types using the JDBC driver?

--
Regards,
Richard Broersma Jr.

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: [JDBC] Comparing Enumerated Types between JDBC and ODBC drivers

Hi,

First, You need to distinguish between SQL COMPLEX / COMPOSITE types=20
(sometimes called as UDT) and PSQL internal types. Interval is internal=20
type, such like integer, varchar, etc and it's mapped in JDBC to Java=20
object from PSQL JDBC api. There is no public (JDK, OO, SUN) for=20
Interval, but you have right in your situation you can get this type by=20
calling getString() and you will get it's compatible representation, as=20
well setString() should store those, too. You can find internal types=20
which doesn't have mapping to any Java class, too.

If you want SQL COMPOSITE types, only one way to access them (as I=20
think), is similarly, by get/set String. JDBC driver doesn't support=20
custom mapping of UDT to Java classes.

It's looks ODBC driver has better support for PSQL.

Kind regards,
Radosław Smogura

On Tue, 21 Dec 2010 10:14:18 -0800, Richard Broersma=20
wrote:
> While testing the waters of porting a MS-Access application to=20
> OObase.
> I noticed that certain types such as Enumerated types - as well as
> other types (i.e. interval), where not representable in OObase using
> the JDBC driver. However, when I used the ODBC driver for OOBase=20
> all
> such types were once again representable (they were represented as
> text).
>
> Is this an issues with OOBase or an issue with the representation of
> complex types using the JDBC driver?
>
> --
> Regards,
> Richard Broersma Jr.


--=20
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: [JDBC] Comparing Enumerated Types between JDBC and ODBC drivers

On Wed, Dec 22, 2010 at 6:11 AM, Radosław Smogura
wrote:

> If you want SQL COMPOSITE types, only one way to access them (as I think),
> is similarly, by get/set String. JDBC driver doesn't support custom mappi=
ng
> of UDT to Java classes.
>
> It's looks ODBC driver has better support for PSQL.

I think I understand. Would you say that the underlying issue here is
the difference between the JDBC and ODBC specification?


--=20
Regards,
Richard Broersma Jr.

--=20
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc