While it would be duplication, you could consider putting the unique
controlling properties into an additional column - therefore probably
not causing harm to existing components...
On Nov 28, 2005, at 7:17 AM, Ondra Cada wrote:
Anjo,
On 28.11.2005, at 13:00, Anjo Krank wrote:
Refactor your table and move the unique stuff to an extra table
and enforce the DB-level uniqueness there?
Hmm... can be done of course, but at the first look it seems to me
a bit on the complex side: to re-factor the database and to write
the Java glue to make two different attributes look like just one
with two different kinds of values and so forth just to make one
save-and-test atomical? Moreover, I am not designing: the
application already runs; making some values in one column--which
already exists--unique is a change request.
Anyway thanks a lot: I haven't considered this possibility. Perhaps
it will prove to be the best one.
---
Ondra Čada
OCSoftware: [EMAIL PROTECTED] http://www.ocs.cz
private [EMAIL PROTECTED] http://www.ocs.cz/oc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/lists%
40anderhome.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
