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: Theodore Petrosky <email@hidden>
- Date: Sun, 16 Dec 2012 13:43:35 -0800 (PST)
I may try that next time. However, there are times that I use migrations to alter the database structure. Maybe there was an easier way, but I read a column out to a file, created a new column of the type I wanted, read the file and pushed the data into the new column, then dropped the old column.
Ted
--- On Sun, 12/16/12, email@hidden <email@hidden> wrote:
> From: email@hidden <email@hidden>
> Subject: Re: Simple question: inserting data right after table creation (on migration?)
> To: "Johnny Miller" <email@hidden>
> Cc: "James Cicenia" <email@hidden>, "WebObjects Development" <email@hidden>
> Date: Sunday, December 16, 2012, 4:08 PM
> Two additional
> things about doing it in this method is that you have access
> to EOF so you don't have to use the utilities or raw SQL
> and it is run at the end of ALL migrations, so you know your
> database will be completely migrated when your
> PostMigrations are run.
> SecretPal has some nice examples showing its
> use.
> David
> On 2012-12-16, at 12:45 PM, Johnny Miller <email@hidden>
> wrote:
> You can also
> make your migration file implement: IERXPostMigration
> So in your normal migration do your
> database changes and then in public void
> postUpgrade(EOEditingContext editingContext, EOModel model)
> do your inserts.
>
>
>
>
>
>
> Aloha,
>
>
>
>
> Mr. Johnny Miller
>
> Web Development Manager
>
> Kahalawai Media Company
>
> Lahaina, HI 96761
>
> tel: (808) 661-7962 | mobile: (808) 283-0791
>
> website | e-mail
>
>
>
>
>
>
>
>
>
> On Dec 16, 2012, at 4:34 AM, James Cicenia <email@hidden>
> 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
>
>
> _______________________________________________
> 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
>
>
> -----Inline Attachment Follows-----
>
>
> _______________________________________________
> 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