My SQLAlchemy tutorial proposal was also accepted. (Tutorials are
three hours long and take place the day before PyCon proper.) The
full list of tutorials is here: http://us.pycon.org/TX2007/Tutorials
Here was my proposed outline. (Suggestions welcome before I put this
up on the public wiki. :
Oops, put the first table schema with the code by mistake.
Anyway, I realized I can work around this by explicitly specifying the
columns and foreign keys for just the association table, instead of
autoloading them. Then I can remove all the primaryjoin and
secondaryjoin stuff, and it works fine
hi all,
I'm working on a project with an existing SQLite database whose design
I can't change (F-Spot's photo db). The foreign key relationships are
not labeled as such in the tables themselves, so I have to manually
specify them in my mappers. I'm not able to get the many-to-many
relationship
oh, i forgot - theres one thing that could produce significant speed
changes, which is if youre using any PickleTypes anywhere. the
comparison method in PickleType by default now does the long procedure
of pickling both instances and comparing the strings, so that deep
instance changes get picked
you like that, ok. add a ticket (and a doc patch too if you want) to
trac, best way to remind me.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy
obviously you need to forward along that test case. i have no idea
what changed in 0.2.8 to 0.3 that could be slowing it down like that
without seeing some actual code. there have been plenty of major
changes (but none come to mind with regards to object creation).
also, id say dont use t
Hello,
I just wanted to let know that I'm fully using "None" as a Column type
when the column is a "ForeignKey". This feature doesn't seem to be
documented in the doc and I thought I would remind Michael Bayer to make
an update. It keeps your tables clean from redundancy.
Initial topic was "a
On 11/30/06, Sébastien LELONG <[EMAIL PROTECTED]> wrote:
> So, SA 0.2.8 is, in my case, approx. 6-7 times faster than SA 0.3.1.
> The test is exactly the same (same test fixtures, same database, same
> libs, ...), except SA lib version. Both extraction and storage are slower.
>
> FWIW, the data mo
On 11/30/06, che <[EMAIL PROTECTED]> wrote:
>
> hello.
>
> Some rambling on the ORM-layer.
>
> We have our own self-awareness framework (e.g. active-record-like
> metadata-keeping - attributes, types, validation, ...), it's called
> StaticType as it does just that - structures defined through it a
because of the circular reference between two rows, you have to use the
post_update flag on one of the relations. complicating that is that
you are using backreferences, which means the backref relationship on
the post_update relation also needs to be explicitly spelled out (i
might want to chang
hello.
Some rambling on the ORM-layer.
We have our own self-awareness framework (e.g. active-record-like
metadata-keeping - attributes, types, validation, ...), it's called
StaticType as it does just that - structures defined through it are
staticly-typed; no dynamic attributes, and no __dict__
Hi,
i saw the example for the above in the:
http://permalink.gmane.org/gmane.comp.python.sqlalchemy.user/3713
but after several trials to map the tables did not succeed.
The example code below demonstrates the problem - I create 2 objects
that are interconnected and sqlalchemy generates insert for
12 matches
Mail list logo
