MySQL returns the tablename if possible otherwise the alias. I find
this an acceptable solution. Having at least a name one could query the
meta system in other to determine whether it is a table name or not.

I am working on automatically generated web interface on the basis of a
single SQL query. This is why I need to know the columns and tables
involved in the query: http://www.melstra.nl/test/Form1.php

Best regards,

Alex Stienstra.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Hi, Alex,

Alex Stienstra wrote:
> MySQL returns the tablename if possible otherwise the alias. I find this
> an acceptable solution. Having at least a name one could query the meta
> system in other to determine whether it is a table name or not.

The problem is that PostgreSQL does not pass any information about
aliases down to the client.

So we have two possibilities to implement this feature: Hack up the
server to provide that additional info, or implement a fully-fledged SQL
parser in the client and get the alias names ourselves.

Both seems not worth it currently.

HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On 22-Sep-06, at 9:23 AM, Markus Schaber wrote:

> Hi, Alex,
>
> Alex Stienstra wrote:
>> MySQL returns the tablename if possible otherwise the alias. I
>> find this
>> an acceptable solution. Having at least a name one could query the
>> meta
>> system in other to determine whether it is a table name or not.
>
> The problem is that PostgreSQL does not pass any information about
> aliases down to the client.
>
> So we have two possibilities to implement this feature: Hack up the
> server to provide that additional info, or implement a fully-
> fledged SQL
> parser in the client and get the alias names ourselves.
Certainly parsing the SQL is expensive, however I would like to see
the server extend the protocol to give us this information.

Dave
>
> Both seems not worth it currently.
>
> HTH,
> Markus
> --
> Markus Schaber | Logical Tracking&Tracing International AG
> Dipl. Inf. | Software Development GIS
>
> Fight against software patents in Europe! www.ffii.org
> www.nosoftwarepatents.org
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that
> your
> message can get through to the mailing list cleanly
>


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hi Markus,

I'am surprised that PostgreSQL doesn't pass the table informatie to the
client. Susprised, since for example the library PHP (pg_field_table) is
using, does pass on this information. I'am quite sure that this library
function is based on the same API as the JDBC implementation is.

I agree with you that PostgreSQL server should supply this information
and implementing a full-flegded SQL parser is no option. Specially,
because PostgreSQL already parses the statement and therefore knows the
tables and columns that are involved in the query.

It is a pitty that this (for me) vital information is not made
available.

Best regards,

Alex.

-----Original Message-----
From: pgsql-jdbc-owner@postgresql.org
[mailtogsql-jdbc-owner@postgresql.org] On Behalf Of Markus Schaber
Sent: vrijdag 22 september 2006 15:24
To: pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] ResultSetMetaData.getTableName() == null


Hi, Alex,

Alex Stienstra wrote:
> MySQL returns the tablename if possible otherwise the alias. I find
> this an acceptable solution. Having at least a name one could query
> the meta system in other to determine whether it is a table name or
> not.

The problem is that PostgreSQL does not pass any information about
aliases down to the client.

So we have two possibilities to implement this feature: Hack up the
server to provide that additional info, or implement a fully-fledged SQL
parser in the client and get the alias names ourselves.

Both seems not worth it currently.

HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings