Hi Michael
2008/7/18 Michael Bayer [EMAIL PROTECTED]:
On Jul 18, 2008, at 9:37 AM, Ryan Tracey wrote:
sqlalchemy.exc.NoSuchTableError: manufacturer
Just to sum up:
dbengine = create_engine('mysql://u:[EMAIL PROTECTED]/schema1')
meta = MetaData()
meta.bind = dbengine
Table('tableX',
Hello Guys,
I have an object which I save to the database using SQLAlchemy, the class is
defined using declarative and has a whole bunch of properties.
This object has one property though which isn't saved to the database, but
to the file system. It is basically a binary string of a files
Yeah thats kind of what I'm trying to do, i think it would help me a little.
Thanks.
--~--~-~--~~~---~--~~
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
Hi
What is the most elegant way of performing a SELECT DISTINCT on a
single column at the ORM level on SQLAlchemy 0.4.6?
It looks like you can do
q=session.query(Order.support_manager).distinct() in the beta
version. This is not supported in 0.4.6 though.
Thanks in advance
Best regards
Jon
On Jul 21, 2008, at 7:19 AM, jrpfinch wrote:
Hi
What is the most elegant way of performing a SELECT DISTINCT on a
single column at the ORM level on SQLAlchemy 0.4.6?
It looks like you can do
q=session.query(Order.support_manager).distinct() in the beta
version. This is not supported
Hi,
I've done some exploring and found that if I connect to the database
as the schema owner the error goes away. I had been connecting through
a proxy account and this was working fine in 4.3. You can see where
this is tripping up 4.6 from the sql log just after staring the app:
With 4.6:
There have been other reports of this issue, all specific to pyodbc. It
doesn't appear to be an issue with SA, as other MSSQL DBAPI modules don't
exhibit the problem.
Please raise the issue on the pyodbc list, I'll work with you if needed to
help resolve it.
Yes it appears to be a pyodbc problem, which is a shame because it's
making debugging my project incredibly difficult (and I've had even
more problems with the other MS SQL libraries like pymssql).
The bug report is here:
I read through the pyodbc forum quickly, and it looks as though this issue,
first reported back in April, cannot be reproduced by the maintainer. Pick
up the forum thread entitled
http://sourceforge.net/forum/forum.php?thread_id=1942313forum_id=550700
pyodbc pops bad exception since
Done - I really hope we can get this fixed because sqlalchemy and
TurboGears is incredibly difficult to use with MS SQL Server at the
moment. I think I may be able to improve sqlalchemy if I can get the
errors propogating properly
Cheers
Jon
the engine does not connect until first used, in this case when you've
called all() on a Query. If you want to force a connection at a
specific point, say engine.connect().
On Jul 21, 2008, at 7:13 AM, Werner F. Bruhin wrote:
Can someone point out to me what I am doing wrong that I can
On Jul 21, 2008, at 9:45 PM, huy do wrote:
Because a mapped class can have an arbitary select as it's source i.e
columns from any table theoretically, it would still be nice to know
exactly which columns were used to map the properties of a given
class. The .c on the model class use to
12 matches
Mail list logo
