Fran what you're talking about is proper ON DELETE CASCADE functionality.  I've seen code to this effect in sql.py and it is mentioned on mentioned briefly on page 138 of the manual.  All you should have to do it setup your references appropriately.

-tim

Fran wrote:
On Dec 16, 10:47 am, billf <billferr...@blueyonder.co.uk> wrote:
  
Personally, I would vote to implement multi-column unique constraints
so that data integrity can be specified completely using DAL syntax
without the need for native SQL.
    

I am at the stage of my app where I need to do a delete on an item
which has records in many tables.
I'd love a DAL-way of doing this without manually having to list each
of the tables which may contain an associated record.
(Since there's a large number of tables which could have such a
record)

I'm not sure what would be required to allow this?

F

  

-- 
Timothy Farrell <tfarr...@swgen.com>
Computer Guy
Statewide General Insurance Agency (www.swgen.com)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to