From e89a00af0b935183af40479f634db0a098c34e4a Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Fri, 9 Mar 2012 09:01:44 +0200 Subject: Don't override NOT NULL on Oracle VARCHAR column if it's primary key --- doc/manual.xhtml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/manual.xhtml b/doc/manual.xhtml index 6257cf7..e14f2cf 100644 --- a/doc/manual.xhtml +++ b/doc/manual.xhtml @@ -13261,10 +13261,13 @@ SHOW integer_datetimes

In Oracle empty VARCHAR2 and NVARCHAR2 strings are represented as NULL values. As a result, - in the generated schema, columns of these types are always - declared as NULL, even if explicitly declared as + in the generated schema, columns of these types are declared as + NULL even if explicitly declared as NOT NULL with the db not_null pragma - (Section 12.4.5, "null/not_null").

+ (Section 12.4.5, "null/not_null"), + except for primary key columns. This also means that for object ids + that are mapped to these Oracle types, an empty string is an invalid + value.

The Oracle ODB runtime library also provides support for mapping the std::string type to the Oracle CHAR, -- cgit v1.1