See discussion on Open Discussion forum.
http://sourceforge.net/forum/message.php?msg_id=43252
Logged In: YES user_id=120069
I have temp. fixed this. It is really up to the orig. author which path he wishes to take.
The inital path I went towards was including a file named [db_const.inc]. Which defined constants including (partial list):
define('SLZ_STR_DB_TABLE_COMMENTS','comments'); define('SLZ_STR_DB_TABLE_PICTURES','pictures'); --snip--
I updated:
slooze.php
to use the constants. However, without looking deeper I determined the problem also persisted in:
slooze_ct_sql.php
Rather than perists the "hacked" constants...I simply uncased the column names (matching postgresql).
Let me know if I can help, I would be more than happy to apply down casing across entire project on all column and table names and post a patch.
I will double check on the casing "inability" with postgresql.
Log in to post a comment.
Logged In: YES
user_id=120069
I have temp. fixed this. It is really up to the orig.
author which path he wishes to take.
The inital path I went towards was including a file named
[db_const.inc]. Which defined constants including (partial
list):
define('SLZ_STR_DB_TABLE_COMMENTS','comments');
define('SLZ_STR_DB_TABLE_PICTURES','pictures');
--snip--
I updated:
slooze.php
to use the constants. However, without looking deeper I
determined the problem also persisted in:
slooze_ct_sql.php
Rather than perists the "hacked" constants...I simply
uncased the column names (matching postgresql).
Let me know if I can help, I would be more than happy to
apply down casing across entire project on all column and
table names and post a patch.
I will double check on the casing "inability" with
postgresql.