On Thu, 15 Nov 2007 10:09:08 -0500, Michael Bayer [EMAIL PROTECTED] wrote:
[On Session.mapper]
it would be easier if you just didnt use autosave, id really love to
remove that feature entirely.
IMO removing that functionality would make SQLAlchemy a lot more awkward to
use. /me votes
I noticed that the path_based_options branch has been merged, which
looks great as a way to eager-load deep relationships in queries built
with from statements (ie: query.from_statement). I noticed some
strange behavior and I want to check that I've got the right idea
before I open any tickets:
Hi.
I have found an insidious problem with SQLAlchemy and PostreSQL.
Here is an example:
from sqlalchemy import engine, schema, sql, types
metadata = schema.MetaData()
a = schema.Table(
'a', metadata,
schema.Column('id', types.Integer, primary_key=True),
schema.Column('x',
On Nov 16, 2007, at 1:54 PM, Manlio Perillo wrote:
There is an error in the schema, b.id is of type String instead of
type
Integer.
Unfortunately PostgreSQL does not raises an error, but just a warning.
In fact I have found such a problem in one of my programs only after a
pg_dump +
On Nov 15, 2007 1:43 PM, Michael Bayer [EMAIL PROTECTED] wrote:
yes, this was in my previous email:
We
might look into changing that to an OracleDateTime for autoload=True
on the next release. In the meantime, override your reflected DATE
column with an OracleDateTime type.
though
Howdy Group,
Let's say I have a very simple query: select person.id, person.name,
person.age from person
Can I remove one of the columns, say person.age, from this result
set and still use the list as a RowProxy? I'm trying to do it now and
it's not working. I'm creating a new list and
