On Jan 26, 2007, at 6:05 PM, Jonathan Ellis wrote:
On 1/26/07, Michael Bayer [EMAIL PROTECTED] wrote:
doing away with the __del__() thing ? what would we gain by
removing the __del__() call ?
relying on it is buggy. so why have it?
youre basically saying, do away with implicit
i have some notes on how to create instances that are unique to some
identity:
http://www.sqlalchemy.org/trac/wiki/UsageRecipes/UniqueObject
as far as it being a list of normal strings, thats a feature we
havent implemented as of yet. hibernate does it, you can make
collections of ints
On 1/26/07, Michael Bayer [EMAIL PROTECTED] wrote:
On Jan 25, 7:28 pm, Allen [EMAIL PROTECTED] wrote:
The basic idea of a persistence layer (as I understand it) is that you
attempt to isolate applications from the database to the point that the
application and the data model can vary
On 1/27/07, Allen Bierbaum [EMAIL PROTECTED] wrote:
I agree that a complete separation is probably either a) impossible or
b) going to lead to code that is so complex and difficult to maintain
that it removes any advantage gained.
I modify the schema and code in step during development, once
On Jan 27, 2007, at 11:57 AM, Allen Bierbaum wrote:
As a side note, I am trying to see where ActiveMapper would fit into
all of this. At first I thought that ActiveMapper would actually tie
the classes closer to the data model, but after looking at it further
I am starting to think that it
the polymorphic join is fine. the combination of equivalent columns
is not an issue. the creation of the query is built against a
particular mapper's selectable; when a row from that query is passed
to a different mapper due to a polymorphic switch, the row is
translated to be against the
thanks i added ticket #444 to remind me to put this one in
On Jan 24, 7:56 pm, Peter Nixon [EMAIL PROTECTED] wrote:
On Wed 24 Jan 2007 00:37, Michael Bayer wrote:
no, youre testing it for me first :)Well it seems to work ok :-)
Thanks
--
Peter Nixonhttp://www.peternixon.net/
PGP
Well in this case, the Tag class is really unnecesseary
--~--~-~--~~~---~--~~
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
So, ive been working on this crapola pretty much all day...
(YOURE WELCOME) ...
and the latest is in a branch http://svn.sqlalchemy.org/sqlalchemy/
branches/polymorphic_relations .
so, the one thing i really cannot crack at all is how to make
polymorphic_union figure out the dupe
