PEAR is archived and read-only

This mirror preserves historical PEAR package releases and metadata so existing references remain available.

Home » Authentication » LiveUser » Bug #2002

Column 'group_define_name' cannot be null

Details

Request #2002Column 'group_define_name' cannot be null
Submitted2004-07-28 04:18 UTC
Fromworker at mompopmedia dot com
StatusClosed
PackageLiveUser
PHP Version5.0.0
OSMandrake 10
Roadmaps(Not assigned)

Comments

[2004-07-28 04:18 UTC] worker at mompopmedia dot com

Description:
------------
addGroup() parameter $define_name defaults to null is not set. This results in the following sql being built:

INSERT INTO
user_groups
(group_id, group_type, group_define_name, is_active,owner_user_id,owner_group_id)
VALUES
(
4,
NULL,
NULL,
'Y'
,NULL,NULL)

This SQL will fail, as the column group_define_name is a "not null" column (at least this is how it is defined in the bundeled sql).

[2004-07-28 04:59 UTC] worker at mompopmedia dot com

i left it to the defaults:

...
'permContainer' => array(
'connection' => &$fw_db,
'type' => 'MDB2_Complex',
'prefix' => 'user_'
)
...

[2004-07-28 20:33 UTC] smith at backendmedia dot com

We dont have default values for the permContainer option. FYI we also dont have default values for the authContainers option.

Again have a look in the LiveUser.php to see a sample conf array. Also if you have a look at the $_options property for all the default values.

[2004-07-28 20:45 UTC] smith at backendmedia dot com

Ok I am reopening this as a feature request. We already have default values in the auth containers. However they are useless as they need to be overwritten in order to pass a connection or dsn. So we would need to explicitly clobber the defaults with the options passed by the user using LiveUser::arrayMergeClobber().