Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Fields declared as NOT NULL
Wed, Jun 15 2011 5:33 AMPermanent Link

Rony Gellaerts

Tim,

EDB 2.05b9 (UNI)
Win7 prof (32bit)

I have a field declared as

"Document" VARCHAR(150) COLLATE "UNI_CI" NOT NULL

I have created a stored procedure to insert a new record. When i now execute the procedure from within EDBManager and leave the parameter value for 'Document' to NULL, there should be an error generated saying that the field may not be NULL. Instead EDBManager reports that the procedure is executed successfully, but nothing is inserted.
Executing the stored procedure from my application, gives me a new record but with de "Document" field empty.

The same with
"Datum" DATE,
"Jaar" VARCHAR(4) COLLATE "UNI_CI" GENERATED ALWAYS AS CAST(EXTRACT(YEAR FROM Datum) AS VARCHAR(4))  NOT NULL

(I know, field "Datum" should also be declared as NOT NULL)

Regards,
Rony Gellaerts
Wed, Jun 15 2011 2:46 PMPermanent Link

Uli Becker

Rony,

> Instead EDBManager reports that the procedure is executed successfully,
but nothing is inserted.
> Executing the stored procedure from my application, gives me a new record but with de "Document" field empty.

I just tested this with the same build (but non Unicode) and it works
like expected for me (exception is raised).

Regards Uli
Wed, Jun 22 2011 6:57 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Rony,

Resolved via email - issue was with the stored procedure not re-raising
exceptions in its EXCEPTION block.

--
Tim Young
Elevate Software
www.elevatesoft.com
Image