web2py is multiplatform. it behaves in the same exact way in every os it
runs into.
On Friday, February 15, 2013 11:25:10 PM UTC+1, Hector Magnanao wrote:
>
> Will these options also work for database that is on a linux server ?
>
> On Friday, February 15, 2013 10:44:05 AM UTC-6, Hector Magnanao wrote:
>>
>> Awesome !!! Option 2 worked. Thanks.
>>
>> On Friday, February 15, 2013 10:00:54 AM UTC-6, Niphlod wrote:
>>
>>> yep, but you have either to:
>>> 1. copy over the databases/ folder (the .table files holds the state of
>>> the tables on the db as far as web2py knows, so the 2nd one if doesn't find
>>> the table files thinks it has to create them)
>>> 2. set migrate=False for the tables on the 2nd app (so web2py will trust
>>> your models and never try to create any table). Usually on the 2nd app you
>>> want to do
>>> db = DAL('same uri as the one for the 1st app', migrate_enabled=False)
>>> ##optionally auth.define_table(migrate=False)
>>>
>>> 3. fake migrate all the tables on the 2nd app (so web2py will trust that
>>> the current model is in sync with the db and recreate the .table files)
>>> db = DAL('same uri as the one for the 1st app', fake_migrate_all=True)
>>> then hit the appadmin (one time only is enough to create the files),
>>> then continue with
>>> db = DAL('same uri as the one for the 1st app')
>>>
>>> I vote for 2.
>>>
>>>
--
---
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
