Closed (fixed)
Project:
Category
Version:
master
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 Mar 2006 at 10:54 UTC
Updated:
28 Apr 2006 at 14:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Anonymous (not verified) commentedThe tables will need some changes to work properly on postgresql. One of the tables has no primary key defined? which PostgreSQL doesn' t like and the indexes need to be declared seperatly. I have had it running under postgreSQL, just the tables need a few tweaks.
Comment #2
Jaza commentedYou've had it running under PostgreSQL? Great! It would be great if you could post the SQL
CREATE TABLEstatements that you used, as well as reporting any problems that you may have had with the SELECT / INSERT / UPDATE / DELETE statements within the module.Comment #3
Anonymous (not verified) commentedThis should get it working on PostgreSQL. The only problems are nodes are not being linked to categories and PostgreSQL does support sequences, as a database feature, but does not use the sequences table like MySQL. The SERIAL data type is set in the category table, so categories get a unique ID. Most of the functionality works under PostgreSQL, but its not linking to anything else yet.
Comment #4
Anonymous (not verified) commentedNew SQL for recent updates, seems to work. The nodes seem to stick to categories now, maybe the container was configured wrong. Only thing is the sequence SQL and its listing the node types allowed in a container twice though it only stores the it once in the database.
Comment #5
Jaza commentedDB install script committed to HEAD. I have noticed some problems with some queries that are run when using category (post-install), but the install script itself seems to be fine.
Problems with other queries within the category package should be filed as separate issues, as this issue is related to the initial creation of the install script (which is now done).
Comment #6
(not verified) commented