articlecontent table structure...?
Posted: Fri 12. Dec 2003, 14:25
Hi All,
Firstly, I'm very impressed with phpWCMS - it fills my requirements (nearly) exactly.
I'm currently setting up a site at http://www.soton.ac.uk/~crc100 which will, when it has enough content, be moved to http://www.soton.ac.uk/~stagesoc. As is implied in the address it resides on the University of Southampton (UK) servers, and in their wisdom (and I can see their point really) I only have access to Oracle. The phpWCMS you see is running off Oracle (after much hard work).
phpWCMS has a column per content type in the phpwcms_articlecontent table. I was wondering why this was. Oracle only lets you use 1 'long' data type per table, which means that I can only use 1 data type - unless, I modify all the INSERT/UPDATE statements to use the same column, which, since there is an acontent_type column as well, works fine.
I don't want to mess the code up too much though - for upgrading purposes.
Despite the effort required to change all the code from mySQL to Oracle - I believe it was worth it, and if anyone wants help doing the same - feel free to ask.
Chris Copsey.
Firstly, I'm very impressed with phpWCMS - it fills my requirements (nearly) exactly.
I'm currently setting up a site at http://www.soton.ac.uk/~crc100 which will, when it has enough content, be moved to http://www.soton.ac.uk/~stagesoc. As is implied in the address it resides on the University of Southampton (UK) servers, and in their wisdom (and I can see their point really) I only have access to Oracle. The phpWCMS you see is running off Oracle (after much hard work).
phpWCMS has a column per content type in the phpwcms_articlecontent table. I was wondering why this was. Oracle only lets you use 1 'long' data type per table, which means that I can only use 1 data type - unless, I modify all the INSERT/UPDATE statements to use the same column, which, since there is an acontent_type column as well, works fine.
I don't want to mess the code up too much though - for upgrading purposes.
Despite the effort required to change all the code from mySQL to Oracle - I believe it was worth it, and if anyone wants help doing the same - feel free to ask.
Chris Copsey.