I definitely can - I'll let you know what I find. -N
On Jul 15, 1:05 am, mdipierro <[email protected]> wrote: > If not it is a bug. Can you help debug this? > > On 14 Lug, 22:33, NiallSweeny <[email protected]> wrote: > > > > > Does this work with Oracle databases? I have defined a table as > > such: > > > db.define_table('MITED_ROLE', Field('MITED_ROLE_ID', 'id'), > > migrate=False) > > > ... and get the error: ORA-00904: "MITED_ROLE"."ID": invalid > > identifier which seems to me to say that it's not using my > > MITED_ROLE_ID field as theidfield. > > > ? > > > On Jul 12, 3:28 pm, mdipierro <[email protected]> wrote: > > > > No need. You should be able to just do > > > > db.define_table('property',Field('PropertyID','id'),....) > > > > i.e. add an extra field of type 'id' with the proper name. Let us know > > > if this works. > > > > Massimo > > > > On 12 Lug, 13:32, Michael Wolfe <[email protected]> > > > wrote: > > > > > I have dozens of tables in an existing MSSQL database all with > > > > autonumberIDprimary keys, but none that are named 'id'. They are > > > > instead named PropertyID, ClientID, etc. The official documentation > > > > seems to suggest renaming each of these fields to 'id'. However, that > > > > would require breaking hundreds of existing queries in other > > > > applications that use this database. Surely there must be some way to > > > > specify a name for an existing autonumber field to be used instead of > > > > 'id'. > > > > > I'd really like to try web2py because it seems well thought-out, but > > > > if this is not possible it is a deal-breaker for me and I'll have to > > > > go back to Django (at least for this project...and any other future > > > > project that must supportlegacydatabases). > > > > > Thanks, > > > > -Mike
