Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PreparedStatement.getMetaData() and Creator
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Jeremiah Jahn <jeremiah(at)cs(dot)earlham(dot)edu>
- Cc: postgres jdbc <pgsql-jdbc(at)postgresql(dot)org>
- Subject: Re: PreparedStatement.getMetaData() and Creator
- Date: Thu, 29 Jul 2004 13:23:46 -0500 (EST)
- Message-id: <Pine.BSO.4.56.0407291307090.9250@leary.csoft.net> <text/plain>
On Thu, 29 Jul 2004, Jeremiah Jahn wrote: > >We just tested postgresql in house and found that the driver is > >returning null for PreparedStatement.getMetaData() > It may be possible to do that now. Previously PreparedStatements were implemented by doing the substitution on the driver side and sending the full query to the backend, so the only way to get the metadata was to actually run the query. With the new V3 protocol support it seems possible to issue Parse and Describe messages without issuing Bind or Execute. Kris Jurka
- References:
- PreparedStatement.getMetaData() and Creator
- From: Jeremiah Jahn
- PreparedStatement.getMetaData() and Creator
- Prev by Date: Re: Wrong column names in ResultSetMetaData
- Next by Date: Re: Bug in 7.4_213 driver: returns VARCHAR instead of
- Previous by thread: PreparedStatement.getMetaData() and Creator
- Next by thread: Re: Java Studio Creator and postgresql jdbc
- Indexes: