Bug #368

More Oracle compatibility issues

Details

Submitted	2003-12-06 01:50 UTC
From	kipaten21 at hotmail dot com
Assigned	lsmith
Status	Closed
Package	LiveUser
PHP Version	Irrelevant
OS	ANY
Roadmaps	(Not assigned)

Comments

[2003-12-06 01:50 UTC] kipaten21 at hotmail dot com

Description:
------------
There are issues with the way Oracle handles the "is_active" columns in tables LIVEUSER_USERS and LIVEUSER_GROUPS.

The columns are of type CHAR(1), meant to accept the character 'Y' or 'N'.

Queries in several methods from all classes in "Admin/Perm/Container/" use double quotes around the Y or N character (since the $query variable is contained within single quotes) which throws an error in Oracle. Apparently, Oracle only allows the use of double qoutes in a query for strings and requires single quotes if the value is a single character.

This issue might also appear in other LiveUser classes, not just the Admin classes.

Suggest replacing double quotes with escaped single quotes if the variable in contained within single quotes, otherwise just replace double quotes with single quotes.

[2003-12-12 19:51 UTC] anon at anon dot com

Found one that was missed.

_updateImpliedStatus() in Admin/Perm/Container/DB_Complex.php

$query = 'UPDATE
' . $this->prefix . 'rights
SET
has_implied = "' . (((int)$count > 0) ? 'Y' : 'N') . '"