On 27/11/2007, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
> On Nov 27, 2007, at 11:30 AM, Yuri Pimenov wrote:
>
> >> Quote it.
>
> oh right, duh, let me answer post-coffee next time
>
> SQLite is the reason for the truncation on the dot, and I got both
> test cases (i.e. using sqlite and you
On Nov 27, 2007, at 11:30 AM, Yuri Pimenov wrote:
>> Quote it.
oh right, duh, let me answer post-coffee next time
SQLite is the reason for the truncation on the dot, and I got both
test cases (i.e. using sqlite and you dont expect the dot, or using
dot-separated labels and you do expec
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 ma
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 co
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 becaus
