Setting the driver and plugin in the connection dictionary solved the problem.
Shame on me.
> Em 01/05/2015, à(s) 23:41, Chuck Hill escreveu:
>
> Using a very, very old Wonder I see this
>
> CREATE TABLE "_dbupdater" (
> "lockowner" VARCHAR(100),
> "modelname" VARCHAR(100) CONSTRAINT NOT_NUL
Using a very, very old Wonder I see this
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__dbupdate
For instance, this
"modelname" VARCHAR(100) CONSTRAINT NOT_NULL__dbupdater__modelname NOT NULL,
should be
"modelname" VARCHAR(100) _dbupdater.modelname NOT NULL,
and this
ALTER TABLE "_DBUPDATER" ADD CONSTRAINT "PRIMARY_KEY__dbupdater_modelname"
PRIMARY KEY ("MODELNAME") NOT DEFERRABLE INITI
I am not seeing anything wrong there.
On 2015-05-01, 7:11 PM, "Ângelo Andrade Cirino" wrote:
I've been using migrations for a long time, but today I had a problem that left
me completely in the dark. See the SQL being generated:
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE, LOCKING PESSIMISTIC;
I’ve been using migrations for a long time, but today I had a problem that left
me completely in the dark. See the SQL being generated:
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE, LOCKING PESSIMISTIC;
CREATE TABLE "_dbupdater" (
"lockowner" VARCHAR(100),
"modelname" VARCHAR(100
