Index: openacs-4/packages/acs-core-docs/www/db-api.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/db-api.html,v diff -u -r1.53 -r1.54 --- openacs-4/packages/acs-core-docs/www/db-api.html 25 Apr 2018 08:38:27 -0000 1.53 +++ openacs-4/packages/acs-core-docs/www/db-api.html 12 Feb 2019 17:12:18 -0000 1.54 @@ -339,27 +339,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@@ -545,25 +524,6 @@
Technically it's equivalent to using a code block on the end of your db_multirow.
-
- 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.
-