Michael,
Thanks for the quick reply, I needed a bit of time to be able to get
some more data on this.
Michael Bayer wrote:
...
uh it depends on what object.otherviewofsubobject is...is that a
relation() ? a python descriptor ? if the latter, how does it
work ? where does it get
Hi.
I want to add a set of common columns for a set of tables. For
example, given tables
personal_profile(name, nickname, fav_color ...)
professional_profile(work, location, designation ...)
I want to add auditing columns to both of these, like so -
personal_profile(*created_on*,
On Sat, 10 May 2008 14:06:12 +0530
Sandesh Singh [EMAIL PROTECTED] wrote:
It would be best if the auditing columns could be defined in one
place, and then added to all the tables individually. I believe the
solution may have more to do with Python than with SQLAlchemy itself.
This is my
On May 10, 2008, at 10:01 AM, Lele Gaifax wrote:
I have another little issue with that: I'd like to be able to say that
those fields behave like a readonly and database-generated value (they
are effectively overwritten by a database trigger, at insert/update
time), possibly without
seems like a bug whereby when it sees the Manager single table
inheritor, it somehow doesn't get the message to synchronize the
Employee primary key column with the Person primary key column.
I'll have a look at it later today.
On May 9, 2008, at 7:49 PM, Fernando Zunino wrote:
Hi,
On May 10, 2008, at 10:22 AM, Yannick Gingras wrote:
I attach a test case. In here, it prints:
--
** q[:0]
SELECT users.id AS users_id, users.name AS users_name
FROM users ORDER BY users.id
** q[0:0]
SELECT users.id AS users_id, users.name AS users_name
very simple and was fixed in r4720.
On May 10, 2008, at 12:48 PM, Michael Bayer wrote:
seems like a bug whereby when it sees the Manager single table
inheritor, it somehow doesn't get the message to synchronize the
Employee primary key column with the Person primary key column.
I'll have
hey list -
as you might have noticed we've merged 0.5 into the trunk. this
version is already spectacular and I encourage everyone to start
poking around.
The migration doc is being developed at
http://www.sqlalchemy.org/trac/wiki/05Migration
. The emphasis in this release is two big
Is the stuff from user_defined_state branch merge in ?
If so is the __sa_instrument_class__ stuff the same ?
Michael Bayer wrote:
hey list -
as you might have noticed we've merged 0.5 into the trunk. this
version is already spectacular and I encourage everyone to start
poking
Trunk Rev 4726
Note the following:
Python 2.5.2 (r252:60911, May 7 2008, 15:19:09)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help, copyright, credits or license for more information.
from sqlalchemy import *
Traceback (most recent call last):
File stdin, line 1, in module
File
Steve Zatz wrote:
Trunk Rev 4726
Note the following:
Python 2.5.2 (r252:60911, May 7 2008, 15:19:09)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help, copyright, credits or license for more information.
from sqlalchemy import *
Traceback (most recent call last):
File stdin,
Thanks!!
On May 10, 2:42 pm, Michael Bayer [EMAIL PROTECTED] wrote:
very simple and was fixed in r4720.
On May 10, 2008, at 12:48 PM, Michael Bayer wrote:
seems like a bug whereby when it sees the Manager single table
inheritor, it somehow doesn't get the message to synchronize the
be sure to clean out the .pyc files.
That worked. 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
To unsubscribe from this
13 matches
Mail list logo
