Re: migrations in framework

Subject: Re: migrations in framework
From: Jeff Schmitz <email@hidden>
Date: Tue, 14 Apr 2009 21:58:19 -0500

I tried turning on the logging:

log4j.logger.er.extensions.migration.ERXMigrator=DEBUG

but I don't get any log messages at all from ERXMigrator.

However, I did just find the ERXMigrator docs, and I'm not doing the following and I'm guessing I need to?...

Because of complications with database locking, the system will not autocreate tables and per-model rows for you, so if you are using JDBC migration, you should create a table named _DBUpdater with the following (approximately) create statement:

               create table _dbupdater (
                 modelname varchar(100) not null,
                 version integer not null,
                 updatelock integer not null,
                 lockowner varchar(100)
               )

I tried it:

log4j.logger.er.extensions.migration.ERXMigrator=DEBUG

But I don't see any debug statements from ERXMigrator.

Howeverand for each model you want to be able to migrate, you should:

               insert into _dbupdater(modelname, version, updatelock, lockowner) values ('YourModelName', -1, 0, NULL)
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

Follow-Ups:
- Re: migrations in framework
  - From: Mike Schrag <email@hidden>

References:
	>migrations in framework (From: Jeff Schmitz <email@hidden>)
	>Re: migrations in framework (From: David Avendasora <email@hidden>)
	>Re: migrations in framework (From: Jeff Schmitz <email@hidden>)
	>Re: migrations in framework (From: Mike Schrag <email@hidden>)

Prev by Date: Re: migrations in framework
Next by Date: Re: migrations in framework
Previous by thread: Re: migrations in framework
Next by thread: Re: migrations in framework
Index(es):
- Date
- Thread