Re: Testing ExpressionFactory for null values

From: Jürgen Saar (jsaa..eb.de)
Date: Thu Apr 07 2005 - 04:06:28 EDT

Next message: tnaki..ofthome.net: "fetch limit"

Previous message: Andrus Adamchik: "Re: Testing ExpressionFactory for null values"
Maybe in reply to: Fredrik Liden: "Testing ExpressionFactory for null values"
Next in thread: Bryan Lewis: "Re: Testing ExpressionFactory for null values"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

dafault values may be a bad design, but there are many
use cases where this makes sense. So it depends on the
usage.

In all cases where null tells you, that this information is not
available, null values are fine.

cayenne-use..bjectstyle.org schrieb am 07.04.05 03:19:37:
>
> Is it possible to test for null values using the in-memory
> ExpressionFactory?
>
> Or is it just bad design to keep default values as null?
> Does anyone have any input?
>
> Thanks!
>
> Fredrik

__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201

Next message: tnaki..ofthome.net: "fetch limit"
Previous message: Andrus Adamchik: "Re: Testing ExpressionFactory for null values"
Maybe in reply to: Fredrik Liden: "Testing ExpressionFactory for null values"
Next in thread: Bryan Lewis: "Re: Testing ExpressionFactory for null values"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Thu Apr 07 2005 - 04:06:46 EDT