Restore of the switch to EOSchemaSynchronizationFactory. Warning:

[spelletier]

The migration can fail with invalid identifier because the column names are not quoted. I searched but cannot find where to fix this problem.

[spelletier]

I spend some time trying to figure where to add the quote on the column identifiers in create table statement without success. The table name itself should also be quoted.

In KAAccessControlDemo, one of the table fail:

CREATE TABLE User(id INTEGER NOT NULL, language VARCHAR(10) NOT NULL, passwordHash VARCHAR(200), username VARCHAR(100) NOT NULL);

User is a reserved word, language is also but is OK in this situation but all identifiers should be quoted.

The primary key generation miss the quote too:
ALTER TABLE UserT ADD PRIMARY KEY (id);

And the foreign Key:
ALTER TABLE KAUserProfile ADD CONSTRAINT KAUserProfile_user_id_id_FK FOREIGN KEY (user_id) REFERENCES UserT (id)

But unique index are OK:
ALTER TABLE "UserT" ADD CONSTRAINT "UNIQUE_UserT__username" UNIQUE("username") DEFERRABLE INITIALLY DEFERRED

Not null constraints are not created with specified names, just NOT NULL added to the column definition.

[spelletier]

The _dbupdater created by the migration class is correctly generated and use the EOSchemaSynchronizationFactory. Table created in my migration class does not.

CREATE TABLE "_dbupdater" ( "lockowner" VARCHAR(100), "modelname" VARCHAR(100) CONSTRAINT NOT_NULL__dbupdater__modelname NOT NULL, "updatelock" INTEGER CONSTRAINT NOT_NULL__dbupdater__updatelock NOT NULL, "version" INTEGER CONSTRAINT NOT_NULL__dbupdater__version NOT NULL )

[rkiddy]

If this is just a revert of a previous commit, can someone pick this up? I would, but I cannot test any FB stuff.

[aacirino]

Perhaps my new pull request have solved the issues reported here. Please refer to #640

[paulhoadley]

By way of update here, #640 was closed without merging, so it won't be helping here.

If this affects only FrontBasePlugIn, and @spelletier uses it and is happy with it, I suggest we merge. I can't test FrontBase, and I don't know that many people can.

[hprange]

Unfortunately, we need to solve the conflicts before merging this pull request. 😕 @spelletier is this pull request still relevant to you? Can you update it if it is? We're going to merge it as long as it has no conflicts and somebody has tested it.