Hello.
Just problem of my ability of English ....
I think it is better to take the extra time up front to address the issue in the best way.
What does "extra time up front" mean ? It seems to have some meaning of period of time ... Is this a set phrase which have special meaning in project ?
If it makes it easier, I personally, think that it would be fine to add another column using the same model as the other autoincrement information. Then, they all can be rolled into DefaultInfo later as part of a separate cleanup task.
I think adding extra information to the DefaultInfo is the correct way and is the way the system was designed. The column's definition is through the interface DefaultInfo, thus allowing different object implementations to be stored in the column, representing additional information as needed.
Thinking freely in these days,
I came to thought it would be worth to rollback to first phase of desicion aboout solution1-3.
As you know, we have three solution.
Implementing for solution-1, we found there exists barrier in implementation of DefaultInfo.
Then , it would be worth to think about solution-2 and solution-3.
Best regards.
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED] Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html*/
----- Original Message ----- From: "Daniel John Debrunner" <[EMAIL PROTECTED]>
To: "Derby Development" <[email protected]>
Sent: Thursday, April 28, 2005 11:00 PM
Subject: Re: Question about softupgrade mode ..
Kathey Marsden wrote:
TomohitoNakayama wrote:
Now, I came to thought changing DefaultInfo have more impact than adding column to SYSCOLUMNS table .... //I wishes that DefaultInfo existed in either case of autoinrement and default !!!
Thinking the autoincrement is one kind of default, I think approach of adding attributes of autoincrement to DefaultInfo is not bad. However , thinking impact of that modification, I think I MUST be at a loss correctly and find the answer for that.
If it makes it easier, I personally, think that it would be fine to add another column using the same model as the other autoincrement information. Then, they all can be rolled into DefaultInfo later as part of a separate cleanup task.
I think adding extra information to the DefaultInfo is the correct way and is the way the system was designed. The column's definition is through the interface DefaultInfo, thus allowing different object implementations to be stored in the column, representing additional information as needed.
Adding a system column with the intention of removing it later as cleanup just seems wrong, I think it is better to take the extra time up front to address the issue in the best way.
Dan.
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.10.4 - Release Date: 2005/04/27
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.10.4 - Release Date: 2005/04/27
