Re: Making columnOriginal and columnNew public

From: Tore Halset (halse..vv.ntnu.no)
Date: Wed Aug 27 2008 - 04:32:58 EDT

  • Next message: Øyvind Harboe: "Re: Making columnOriginal and columnNew public"

    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.
    >
    > If the model has a *larger* size of a text field, then I want to
    > update the database column to be larger.
    >
    > I'm not sure I'm a believer in an automatic way of handling
    > this since there could be a lot of application specific decisions
    > happening.
    >
    > How about exposing the above two attributes in getColumnOriginal()
    > and getColumnNew()?
    >
    > --
    > Øyvind Harboe
    > http://www.zylin.com/zy1000.html
    > ARM7 ARM9 XScale Cortex
    > JTAG debugger and flash programmer
    >

    This archive was generated by hypermail 2.0.0 : Wed Aug 27 2008 - 04:34:19 EDT