Re: Simple question: inserting data right after table creation (on migration?)
Re: Simple question: inserting data right after table creation (on migration?)
- Subject: Re: Simple question: inserting data right after table creation (on migration?)
- From: Flavio Donadio <email@hidden>
- Date: Sun, 16 Dec 2012 12:56:18 -0200
James,
Thanks for the suggestion!
I see a problem with that... If I actually use migrations to modify the tables in future versions of the app, I would need to increment DateModel<x> to DateModel<x+1> every time.
To be true, I don't intend on modifying this app after it's finished, but we never know...
Regards,
Flavio
On 16/12/2012, at 12:34, James Cicenia wrote:
> I have always created a second migration file with SQL inserts. Haven't experienced any problems.
>
> DateModel0 ==> setup tables, etc.
> DateModel1 ==> bootstrap data sql inserts
>
>
>
> On Dec 16, 2012, at 8:23 AM, Flavio Donadio <email@hidden> wrote:
>
>> Hello, people!
>>
>>
>> I think I already know the answer, but I need to check first...
>>
>> I want to create a default user on my WO App when the app is first run. So, I need to create a User entity and insert it right after my tables are created, which is automatically done through a migration.
>>
>> Is it safe to insert my code right after this?
>>
>> userTable.create();
>> userTable.setPrimaryKey("id");
>>
>> Or would I need something else? Is this right, optimal and/or safe?
>>
>>
>> Regards,
>> Flavio
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden