Issue 77 in contentmirror: generated schema incompatible with Pg 8.4

3 views
Skip to first unread message

conten...@googlecode.com

unread,
Feb 5, 2011, 6:55:57 PM2/5/11
to conten...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 77 by d...@tonimueller.org: generated schema incompatible with Pg
8.4
http://code.google.com/p/contentmirror/issues/detail?id=77

./bin/instance run ./bin/mirror-ddl postgresql > mirror.sql

yields code that cannot be run by modern PostgreSQL servers. Issues
discovered so far are:

1. DATETIME -> TIMESTAMP
2. BLOB -> BYTEA
3. BOOLEAN must have values out of (True, False)

Used version: SVN trunk

conten...@googlecode.com

unread,
Aug 24, 2012, 8:27:23 AM8/24/12
to conten...@googlegroups.com

Comment #1 on issue 77 by backup.r...@gmail.com: generated schema
I fixed this by adding an database init script, please see detail in my
contentmirror clone:
https://github.com/lck/ore.contentmirror/commit/41de3897edf726dc86d0e74e2d668672ec4ab585

Problem is that sqlalchemy allways generates generic DDL when using
create_engine with strategy='mock'. I created the init script that directly
updates the database schema, this is the only solution that is worked for
me.

Example:
bin/instance run bin/mirror-init-script.py
postgresql://localhost/contentmirror

and than:
bin/instance run bin/mirror-bulk-script.py MyPloneSite

Regards
R.


Reply all
Reply to author
Forward
0 new messages