Thanks Yarko, much clearer now.
On Oct 21, 1:15 pm, "Yarko T" <[EMAIL PROTECTED]> wrote:
> One more thing: each table in your existing database schema must have a
> unique, auto-incrementing field called "id". If your database does not
> follow this form, you will need to alter it to add such a field.
>
> This is one constraint that web2py imposes.
>
> Also, my previous response should have used the keyword 'False, i.e.
> "....db.table(......, migrate=False)"
>
> On Tue, Oct 21, 2008 at 11:59 AM, Yarko T <[EMAIL PROTECTED]> wrote:
> > You can define a table with "migrate=false" parameter;
>
> > For xxxx.define_table(), you only need to define those things that your
> > web2py applicaiton need to know about - basically, you're defining the
> > interface to the database that you want to have. Turning off migrations
> > keeps from generating the SQL code to update the table schema.
>
> > Hope this helps.
>
> > Yarko
>
> > On Tue, Oct 21, 2008 at 11:27 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> > > wrote:
>
> >> Can web2py's DAL be used without migrations? If I have a pre-existing
> >> database schema, is there a way around using db.define_table? I've
> >> done this with rails by just using empty models.
>
> >> Thanks.
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
