Thanks.
I thought of using pickle but it says not everything can be picked, So
i was concerned the metadata objects might be in the unlucky group.
The other problem i have with pickle is what happens when i upgrade to
a newer version of sqlAlchemy some of the metadata objects might
change. How does pickle handle this?
My other idea instead of pickle was to write code to map it out and
store it in a SQL lite or xml, Then i could patch it so it could be
restored to the never version of sqlAlchemy.
Thanks heaps again for the help,
Regards, Jar
On Nov 29, 1:56 am, Michael Bayer [EMAIL PROTECTED] wrote:
On Nov 28, 2008, at 6:58 AM, [EMAIL PROTECTED] wrote:
Hi All
I'm writing a program for graphically configuring database schemas.
To do this, I want to use the sqlalchemy schema.py objects to store my
metadata as its changed and modified.
To do this, I think i will need three things.
1. Apply the meta data changes to a development database, As this is
the easiest way to ensure integrity as you are reconfiguring the
structure.
2. Store incremental changes to the metadata
3. Snapshot the metadata to a file so it can be restored.
Does SQL Alchemy currently have any facilities to help me achieve
items 2 and 3?
for #1 and #2, you want to use sqlalchemy-migrate
athttp://code.google.com/p/sqlalchemy-migrate/
. For #3, the metadata object can be pickled, and for more
sophisticated serilalization of expression and ORM constructs there is
also a serializer extension in 0.5, documented
athttp://www.sqlalchemy.org/docs/05/plugins.html#plugins_serializer
.
--~--~-~--~~~---~--~~
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 group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---
