Yes, cascades require real foreignkeys in the db, something that mysql only supports if the table's storage engine is innodb. Most mysql servers have the default set at myisam, so foreign keys (and therefore cascading deletes etc) aren't available.
It's good to know that SQLObject handles this for you anyway though :) On 23/11/05, Joost Moesker <[EMAIL PROTECTED]> wrote: > > Oops I have to correct my self here. The cascade option works > perfectly. > > # cascade can be one of: > # None: no constraint is generated > # True: a CASCADE constraint is generated > # False: a RESTRICT constraint is generated > # 'null': a SET NULL trigger is generated > > I mistakenly assumed that the cascade would generate database > constraints (as was the case in the 0.6 release I recall). Yet it > doesn't, the curent version of SQLObjects keeps track of the > dependencies internaly :) > >
