Hi all,

I think I've heard the answer to this in another list, but I just want
to get the widest audience and set of opinions, to be sure..

Apparently right now the V3 protocol doesn't return table-aliases for
columns, like:

select employee.firstName, boss.firstName from contacts as employee,
contacts as boss where employee.bossId=boss.pk AND boss.role = .. AND
employee.role = ...

where on the client we could build a metadata descriptor for each
column, and the table alias for column 1 would return 'employee' and 2
would be 'boss'. (perhaps it should be a separate discussion as to which
the real table name or alias should be returned, if not both - as this
depends on the API/spec)

My question is, is it in *any way* possible to add extra data to V3
without breaking existing clients... so that we can stuff the column
alias into the response.. Or does this really, really need V4?

Since I've been told V3 is prob. not doable, this question certainly
seems to match the 'Hackers' challenge/namesake :)

Thanks in advance,

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

Reply via email to