It may not help in your situation, but did you know that you can also
index the row with the Column instances themselves

Ie: row[table.c.column]

Simon

> -----Original Message-----
> From: sqlalchemy@googlegroups.com 
> [mailto:[EMAIL PROTECTED] On Behalf Of Yuri Pimenov
> Sent: 27 November 2007 16:31
> To: sqlalchemy@googlegroups.com
> Subject: [sqlalchemy] Re: fully qualified column names in RowProxy
> 
> 
> I've found 'use_labels' parameter in select(). Everything is good but
> it uses _ as separator between table and column. That makes things
> not so easy because it is common practice to use _ in table and column
> names.
> Why not to use . as separator?
> 
> My other blue sky dream is about ORM and unicode column names 
> (python3.0?).
> 
> On 27/11/2007, Michael Bayer <[EMAIL PROTECTED]> wrote:
> >
> >
> > On Nov 27, 2007, at 3:04 AM, icct wrote:
> >
> > >
> > > Hi.
> > >
> > > Is there a way to make RowProxy use fully qualified 
> column names like
> > > "table.column"
> > > as keys?
> > > Even if i explicitly label column with "as" in query, 
> RowProxy chops
> > > off anything till last
> > > dot in label.
> > >
> >
> >
> > the reason for that is because in sqlite, if you say 
> "SELECT t2.col3,
> > t2.col4 FROM t2", cursor.description reports the column names as
> > u't2.col3', u't2.col4', instead of 'col3' and 'col4' like 
> every other
> > DBAPI would.......so we truncate against the dot.
> >
> > I did a little testing and I'm not even sure how you'd even make a
> > label with a dot in it;  all three of sqlite, postgres, and mysql
> > raise a syntax error if you try to say "select colname AS
> > tablename.colname from tablename", so thats a pretty decent 
> clue that
> > its not supported by SQL.
> Quote it.
> 
> -- 
> Yuri Pimenov
> 
> > 
> 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to