Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml,v diff -u -r1.17 -r1.18 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml 30 Sep 2018 15:53:28 -0000 1.17 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml 12 Feb 2019 17:12:18 -0000 1.18 @@ -366,27 +366,6 @@ # numeric column "bar") into null in both cases - - - Since databases other than Oracle do not coerce empty strings into - null, this code has different semantics depending on the - underlying database (i.e., the row that gets inserted may not have null as - its column values), which defeats the purpose of SQL abstraction. - - - Therefore, the Database Access API provides a database-independent way to - represent null (instead of the Oracle-specific idiom of the - empty string): db_null. - - Use it instead of the empty string whenever you want to set a column value - explicitly to null, e.g.: - - set bar [db_null] -set baz [db_null] - -db_dml foo_create "insert into foo(bar, baz) values(:bar, :baz)" -# -# sets the values for both the "bar" and "baz" columns to null @@ -590,31 +569,6 @@ - db_null - - - - - - - -db_null - - - - Returns a value which can be used in a bind variable - to represent the SQL value - null. - See Nulls and - Bind Variables above. - - - - - - - - db_foreach