createdb.sql from 2.3: create table weblogcategory ( id varchar(48) not null primary key, name varchar(255) not null, description varchar(255), websiteid varchar(48) not null, image varchar(255) );
createdb.sql from 3.2: create table weblogcategory ( id varchar(48) not null primary key, name varchar(255) not null, description varchar(255), websiteid varchar(48) not null, image varchar(255), parentid varchar(48), path varchar(1000) ); Searching 230-to-320 migration sql script, can't find script for adding column parentid and column path Something may I missing? 2006/11/29, Allen Gilliland <[EMAIL PROTECTED]>:
did you run the 3.1 to 3.2 migration script? it looks like the sql error you got is saying that the new column which was added does not exist. -- Allen long longnan wrote: > Hi, > > Some errors when migrate from 310 to 320. > > Logs list below: > > INFO 2006-11-29 11:41:51,281 UpgradeDatabase:upgradeDatabase - > Database is old, beginning upgrade to version 320 > INFO 2006-11-29 11:41:51,281 UpgradeDatabase:upgradeTo320 - Doing > upgrade to 320 ... > INFO 2006-11-29 11:41:51,281 UpgradeDatabase:upgradeTo320 - > Populating parentid columns for weblogcategory and folder tables > ERROR 2006-11-29 11:41:51,452 UpgradeDatabase:upgradeTo320 - Problem > upgrading database to version 320 > org.postgresql.util.PSQLException: ERROR: column "parentid" of > relation "weblogcategory" does not exist > at > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1525) > > at > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1309) > > at > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188) >
