Maybe that should read: *Currently keyed tables are only supported for DB2, MS-SQL, Ingres and Informix, but others engines CAN be added*.
The biggest hurdle is coming up with the correct syntax to create foreign key (or table) references in a particular database engine. Once you have that then simply modify the adapter class for the database adding the correct 'reference FK' and 'reference TFK' entries in the types dictionary. The adapters are defined in gluon/dal.py, use the entries from any adapter that supports legacy tables as a guide. Then test, test, test. Legacy table support is just great in web2py, even more with the real name parameter <http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer?search=rname#rname--Record-representation> in the table constructor that gets around previous name limitations (thanks Massimo), I use it this a lot. Denes On Thursday, September 4, 2014 5:56:02 PM UTC-4, Anthony wrote: > > From the book: > > > *Currently keyed tables are only supported for DB2, MS-SQL, Ingres and > Informix, but others engines will be added.* > > Aren't other engines supported now as well? > > Anthony > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
