Well then. Based on your description the problem can be restated as
follows:
The way aliases are created by applications is not consistent with the
"description"-field being declared as not-null.
I agree with the comment, made by Gerard vE, that the issue is in the
applications code instead of the oalias field declarations. So of the
solutions you mention, the correct one is obviously:
1) when an alias is created description is set to name (when null)
I see no problems or side-effects to this.
Rob van Maris
Technical Consultant
Quantiq
xmedia & communication solutions
Koninginneweg 11-13
1217 KP Hilversum
T +31 (0)356257211
M +31 (0)651444006
E [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Eduard Witteveen
> Sent: dinsdag 11 mei 2004 15:41
> To: [EMAIL PROTECTED]
> Subject: Re: MMBase 1.7.1 release candidate 1.
>
>
> Rob van Maris wrote:
>
> >Interesting issue. Exactly what has changed between 1.6 and 1.7 to
> >introduce this issue?
> >
> >
> I set not null contrains in the Oracle database layer. IIRC
> these checks
> were also done in the -old- database layer for postgresql, so
> i placed
> them in the Oracle implementation. I dont know whcih checks
> there are in
> the storage layer, but Oracle now checks the following things:
> - not null
> - unique
> - foreign key
> - existence in inherited class
> Or i am mistaken, and this was never checked in the
> postgresql layer, or
> this has been removed in the storage layer and for this reason never
> showed up, untill i started adding contrains on the database.
>
> >Furthermore, I have experienced no problems with importing
> nodes with
> >aliases in an application - is this a database specific issue?
> >
> >
> Well, i guess your database layer does not check on these contrains
