Re: [SQLObject] sqlobject doesn't create foreign keys with MySQL?
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Dan P. <da...@ag...> - 2006-10-26 10:42:53
|
On Thursday 26 October 2006 13:23, Oleg Broytmann wrote: > On Thu, Oct 26, 2006 at 01:06:24PM +0300, Dan Pascu wrote: > > What about defining this new functionality using a different column > > type, say SQLForeignKey or DBForeignKey? > > It would be much harder to support both column. A lot of new code > required. Do you want to work on this? I'm currently just exploring possibilities, but I guess you're right about the complexity. The point is to have both available but not inside the same table so a different column type wouldn't make much sense. So the original idea of having an applyConstraints per table seems fair enough. All I want to see is the current functionality preserved as I use it with tables where foreign keys are not supported and I benefit from SQLObject doing the job itself without the database help. OTOH I really appreciate the fact that native database support for foreign keys is to be implemented for the databases that support this, as this will improve the performance significantly. -- Dan |