the company I worked for has decided to change a RDBMS behind our ERP.
The side effect of this is that the columns will no longer be prefixed
with *t$*
but with* t_* instead. I do not want to change all the occurences of
column
names in my code. I should also mention, that I use only
On Nov 13, 2012, at 5:18 AM, Petr Blahos wrote:
I have been unlucky with mssql, where the first part - the table definition
and making queries worked, but not accessing data in RowProxy using the
key. I guess there is a bug in dialects/mssql/base.py
in MSSQLCompiler.visit_column:
Hi all,
the company I worked for has decided to change a RDBMS behind our ERP.
The side effect of this is that the columns will no longer be prefixed with
*t$*
but with* t_* instead. I do not want to change all the occurences of column
names in my code. I should also mention, that I use only
On Nov 12, 2012, at 5:32 AM, Petr Blahoš wrote:
Hi all,
the company I worked for has decided to change a RDBMS behind our ERP.
The side effect of this is that the columns will no longer be prefixed with t$
but with t_ instead. I do not want to change all the occurences of column
names in
Are there any performance difference between the two?
for row in query_object.all():
do_something()
AND
for row in query_object:
do_something()
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
Hello,
I am pulling a list of files I need to print from a database and I
have all the records after doing the sqlalchemy query with .all()
Now I have a list of 3000 files I need to print, around 3 files per
userID, I want to print all 3 at the same time in different threads,
and my only
Hi gang -
The documentation for 0.4 is undergoing tremendous changes, and is now
released, in its almost-there format, at http://www.sqlalchemy.org/docs/04/
. The goal with these docs is not just to update to new 0.4
paradigms, but to also raise the bar for accuracy and clarity.
Of major note
Hello,
I'm realizing that I've been using .list() to query objects. But all the
examples in the docs talk about .all().
What's the difference ? Should I switch to .all() rather than .list() ?
Will list be deprecated in 0.4 ?
Regards,
--
Alexandre CONRAD
