in this respect web2py works the same as Rail Active Records and Django (if I am not mistaken). This makes life much easier. We are working on a new version of the DAL that will be backward compatible and allow more flexibility.
If you need to access legacy databases the best way is to create a database view for your table. Massimo On Sep 8, 4:52 am, Timmie <timmichel...@gmx-topmail.de> wrote: > > > Do I need to create a ID column before? > > yes > > > Can I define another table field as id? > > no > > May I ask why this is implemented like this? > > For instance in geodata, most data base entries have a unique id > refering to the spatial vector objects. > My current data consits of a list of measurement stations. These have > a unique WMONR. > > Why can I not use that one? > Why do I need to modify the existing table to be compliant with > web2py? > Let's say I would like to share data between a data base created by a > desktop application which uses? > > Why can the id column not be created by web2py when migrate=True is > set? > > Thanks for clarifications in advance. > > Timmie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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 -~----------~----~----~----~------~----~------~--~---
