This is marvellous news. I read the manual last night and realised
that the field ID restriction was the only thing stopping me deploying
web2py in conjunction with a major legacy app that I am using.
Thanks Michael for getting this feature happening.
Can I confirm one thing, with a table like this:
create table store (
ID int,
StoreID int,
Name varchar(60)
)
where I want to use StoreID as the 'id' field, but there happens to be
an existing field called 'ID'.
I have this situation because due to some historical replication
issues.
Chris Guest
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
