[sqlalchemy] Re: Weak Referencing Session

Hi, that the identity map within the Session again becomes weak referencing, the way it used to be back in 0.2 and part of 0.3. +0 from me. It sounds like a sensible change, but I only use short-lived sessions in web apps, so it makes little difference to me. Paul

[sqlalchemy] Re: getattr(myresults,ColumName) vs myresults[ColumnName]

On Sep 12, 2007, at 12:03 AM, Lukasz Szybalski wrote: Currently when you get a record via sqlalachemy you need to take a look at the docs overview (0.4 docs are much better than 0.3s); theres two very different ways to get a record in sqlalchemy. using a SQL expression, you get the exact

[sqlalchemy] Re: Many-to-Many, Column not available

On Sep 11, 2007, at 7:31 PM, KyleJ wrote: I have three rows in the base_table (id's 1-3) and two rows in the relations table. So the row with id 1 in the base_table is linked to the other two rows view two entries in the relations table: INSERT INTO relations (toObj, fromObj) VALUES (2,

[sqlalchemy] Portable exceptions in SA

Hello everybody, I was wondering why neither DBAPI nor SA define standard exceptions like Duplicate key error. It seems to be no portable way to catch this situations and give user more sensible error messages than just We are failed to insert a new record. And using exception information to

[sqlalchemy] Re: Portable exceptions in SA

we do want to get error code availability into our exception classes (still waiting for any DBAPIs besides psycopg2 to provide these with no parsing requirement), and there are some cases where we want to evaulate an exception to discern it from others (such as detecting database

[sqlalchemy] Re: db autogenerated pks?

Still have problems... if i change: t = sa.Table(Machines, metadata, autoload=True) to: t = sa.Table(Rpm_MacchineConfig, metadata, sa.Column('uId', sa.databases.mssql.MSUniqueIdentifier, primary_key=True), autoload=False) i have: sqlalchemy.exceptions.DBAPIError:

[sqlalchemy] Re: Portable exceptions in SA

Michael, Thank you for replying. I think just making few exception classes available would be enough to make some progress. May be some backends would use them without involving too much work and magic. At least people would know there is better way. Even if it would be just psycopg2 for

[sqlalchemy] django + sqlalchemy = ?

Cross-posted to django sqlalchemy lists What is the state of SQLAlchemy integration with Django? I saw somewhere that it was possible to use them together, but the author didn't provide any details, and the SQLAlchemy branch of Django hasn't had any commits since late last year. Was the

[sqlalchemy] Re: Portable exceptions in SA

ANSI defines the SQLSTATE error codes for portable errors. I think there is SQLSTATE support in most of the databases SQLAlchemy supports (but none in SQLite that I can find), and the error code should be available via db-api either directly (pyscopg2, mysql-python, at minimum) or can parsed

[sqlalchemy] Re: db autogenerated pks?

SQL Server provides no facilities for retrieving a GUID key after an insert -- it's not a true autoincrementing key. The MSSQL driver for SA uses either @@IDENTITY or SCOPE_IDENTITY() to retreive the most-recently inserted autoincrement value, but there is no such facility for getting GUID keys.

[sqlalchemy] Re: Portable exceptions in SA

I'd prefer to catch some more specific exceptions even though they'd never be generated by most backends rather than decoding SQLSTATE and use if-s or other dispatching method based on what this variable/ exception attribute holds. On Sep 12, 1:17 pm, jason kirtland [EMAIL PROTECTED] wrote: