Okay, thanks. Done in oracle_create.sql as mentioned, and I'm 
resolving this now.

Well if this constraint is useful for other dbs,

it should be relaxed only for Oracle, of course :-)

It's still a useful constraint for dbs that support the notion of '' 
being different from NULL (which is all of the others that I know). Do 
you really think the constraint should be removed from the general 
scripts, not just the oracle creation script?

Yes there is no distinction on Oracle if you send '' or NULL into VARCHAR.

So removal of the constraint NOT NULL will be necessary for Oracle and 
harmless for other databases.

Well, you can see from that error that we're not sending NULl for that 
column, we're sending ''. I seem to remember something about Oracle 
not having that distinction somehow? I've removed the NOT NULL from 
the oracle_create.sql script, but I'm not sure what else we can do 
about this.

Platform: Apache1.3.31+php4.3.8+Oracle9.2.1



After creating SQL tables and initial configuring HORDE,

the DataTree is empty. If I try to add a permission the following

error occurs (see log entry below). The permission can be added

only after removal of the constraint NOT NULL for column DATATREE_PARENTS.



Sep 17 02:52:45 HORDE [error] [horde] DB Error: null value violates 
not-null constraint: INSERT INTO horde_datatree (datatree_id, 
group_uid, datatree_name, datatree_order, datatree_data, user_uid, 
datatree_serialized, datatree_parents) VALUES (2, 'horde.perms', 
'whups', NULL, 'a:0:{}', 's.rozinov@sibron.ru', 15, '') 
[nativecode=ORA-01400: cannot insert NULL into 
("HORDE3"."HORDE_DATATREE"."DATATREE_PARENTS")] [on line 367 of 
"/var/optpart/local/apache/http/beta.sibron.ru/htdocs/rvs/framework/Horde/DataTree/sql.php"]