Hello.
Done.
https://issues.apache.org/cayenne/browse/CAY-1100
http://svn.apache.org/viewvc?view=rev&revision=689594
Regards,
- Tore.
On Aug 27, 2008, at 08:25, Øyvind Harboe wrote:
I need to figure out if a change to the database would cause data
loss.
E.g. a user might *increase* the s
> I'm leaning towards leaving this in the application domain
I'd have to agree here; schema changes should always be touched by human
eyes, but the only way to do that effectively is at the application
level.
On Wed, Aug 27, 2008 at 10:32 AM, Tore Halset <[EMAIL PROTECTED]> wrote:
> Hello.
>
> (This is related to merging)
>
> Another option to solve the same would be to create a
> AbstractToDbToken.mayRemoveInformation() that all ToDb tokens will have to
> implement? Need to find a better name. What do
Hello.
(This is related to merging)
Another option to solve the same would be to create a
AbstractToDbToken.mayRemoveInformation() that all ToDb tokens will
have to implement? Need to find a better name. What do you think?
Regards,
- Tore.
On Aug 27, 2008, at 8:25 , Øyvind Harboe wrote:
I need to figure out if a change to the database would cause data loss.
E.g. a user might *increase* the size of a text field and in this
case the model should be adapted to the new size. This allows
database managers some control over the database structure
from the comfort of e.g. MS SQL Manager
