Re: EntityModeler not saving "not null" attribute

From: Mike Schrag (mschra..dimension.com)
Date: Mon Dec 17 2007 - 00:59:01 EST

  • Next message: Guido Neitzer: "Re: EntityModeler not saving "not null" attribute"

    I /think/ this should be fixed in tonight's build ... Try opening,
    touching, and resaving your model and see if that works out.

    ms

    On Dec 16, 2007, at 11:06 PM, Guido Neitzer wrote:

    > On 16.12.2007, at 17:29, Mike Schrag wrote:
    >
    >> I would check the definition of your prototype and see if there's
    >> anything weird there. I was just testing with the Wonder
    >> varcharXxx prototypes and created a new entity with two allows null
    >> and one not null attribute, saved, quit, and reloaded it and it was
    >> still set properly.
    >
    > So, what I did to reproduce it:
    >
    > 1. Create a new framework
    >
    > 2. Add a new model
    >
    > 3. Add a new entity
    >
    > 4. Add two attributes, one marked as pk the other as a string (no
    > prototypes involved, no database plugin), the second is set to allow
    > null. This is what I get:
    >
    > attributes = (
    > {
    > columnName = id;
    > externalType = int8;
    > name = id;
    > valueClassName = NSNumber;
    > valueType = l;
    > },
    > {
    > allowsNull = Y;
    > columnName = name;
    > externalType = varchar;
    > name = name;
    > valueClassName = NSString;
    > valueType = S;
    > width = 512;
    > }
    >
    > 5. Remove the checkmark for "allows null" for the second attribute
    > and I get (pk attribute left out):
    >
    > {
    > columnName = name;
    > externalType = varchar;
    > name = name;
    > valueClassName = NSString;
    > valueType = S;
    > width = 512;
    > }
    >
    >
    > Conclusion: nothing with my Prototypes as there are no Prototypes
    > involved, no database plugin, no Wonder, nothing. Just a clean new
    > framework.
    >
    > In the first case I should get a "allowsNull = N" for just the pk
    > attribute, which is not there and in the second case I should get
    > this for the other column, where it said "allowsNull = Y" before,
    > but this information is just removed instead of being changed to
    > "allowsNull = N" - therefor it does not create "NOT NULL"
    > information on schema synchronization and the attributes are not
    > marked as required in my D2W app.
    >
    > Can you reproduce it now?
    >
    > I'm on Leopard, WO 5.3.3, latest WOLips.
    >
    > cug
    >
    > --
    > http://www.event-s.net
    >
    > --
    > http://www.event-s.net
    >



    This archive was generated by hypermail 2.0.0 : Mon Dec 17 2007 - 00:59:52 EST