Here is my initial stab at this:
http://code.google.com/p/sqlitefktg4sa/
Code plus tests.
I welcome your feedback.
On Aug 22, 1:48 pm, jason kirtland [EMAIL PROTECTED] wrote:
Yep, though possibly you'd want it on before-drop. You can actually
handle both tasks in the same function if you
On Wed, Aug 27, 2008 at 3:21 AM, Randy Syring [EMAIL PROTECTED] wrote:
Ok, so I was going to try and implement a solution using the method
discussed here, but ran into a problem b/c I am using Elixir objects
and not declaring the tables directly. Can I still use this method?
How do I get
Gaëtan,
Thank you.
On Aug 27, 5:23 am, Gaetan de Menten [EMAIL PROTECTED] wrote:
On Wed, Aug 27, 2008 at 3:21 AM, Randy Syring [EMAIL PROTECTED] wrote:
Ok, so I was going to try and implement a solution using the method
discussed here, but ran into a problem b/c I am using Elixir objects
Ok, so I was going to try and implement a solution using the method
discussed here, but ran into a problem b/c I am using Elixir objects
and not declaring the tables directly. Can I still use this method?
How do I get the table references from the Elixir objects?
Thanks.
On Aug 22, 1:48 pm,
you can build this functionality using the DDL() construct provided by
SQLAlchemy:
http://www.sqlalchemy.org/docs/05/sqlalchemy_schema.html#docstrings_sqlalchemy.schema_DDL
the ForeignKey objects on the table can be pulled out using:
for c in table.c:
for fk in c.foreign_keys:
DDL() has some simple templating capabilities that can help out a bit
here, but I'd suggest taking the ForeignKey code Mike provided as a
start and putting together an after-create listener using
Table.append_ddl_listener directly:
Thank you, I will look into this.
On Aug 22, 12:44 pm, Michael Bayer [EMAIL PROTECTED] wrote:
you can build this functionality using the DDL() construct provided by
SQLAlchemy:
http://www.sqlalchemy.org/docs/05/sqlalchemy_schema.html#docstrings_s...
the ForeignKey objects on the table
Jason,
Thank you for the response. Using the method you suggest, am I
understanding correctly that fks_for_sqlite() would only be run when a
create() was processed for that table? Also, I am assuming I would
need to create a complimentary function for handling the 'after-drop'
event.
On Aug
Yep, though possibly you'd want it on before-drop. You can actually
handle both tasks in the same function if you like- the event name will
be passed in as the first argument.
Randy Syring wrote:
Jason,
Thank you for the response. Using the method you suggest, am I
understanding