• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ERXMigrationTable.newColumn does not set default value
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERXMigrationTable.newColumn does not set default value


  • Subject: Re: ERXMigrationTable.newColumn does not set default value
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 11 Apr 2008 17:08:19 -0400

Not sure why we didn't do this already :) But then, Anjo will probably respond momentarily and point out that we do :)

It seems to me that this would maintain API compatibility, so the only backwards compatibility issue would be if you try to run these apps on an older WO that doesn't support this mechanism, in which case you'd get null key validation errors. But this seems reasonable to me.

ms

On Apr 11, 2008, at 3:41 PM, Mr. Pierre Frisch wrote:

Both implementation are included. I was thinking of adding a more general mechanism that we could implement in the awakeFromInsertion default implementation. We could add a default value to the attribute and set it in the EOCustomObject in the super method. The main issue is backward compatibility.

Pierre
--
Pierre Frisch
email@hidden


On Apr 11, 2008, at 12:19, Mike Schrag wrote:

Actually it is. The integrated FB plug-in in WO 5.4.x has the same capabilities as the Wonder one. May be we should define an extension to the EOModel format so that we could extent it to all vendors.
I'm not sure about 5.4's implementation, but Wonder has a alternate default value implementation (to maintain backwards compatibility with people who expect the standard FB default behavior). The problem is that the default value as implemented in the FrontBase plugin normally does not pass the default value through the attribute formatter, so if you default value is something other than a String (like a default NSTimestamp), the default value fails. We may be able to just fix the default value interpretation, though, since I actually believe the original is wrong ... I just didn't want to risk breaking someone, so I added an "er.extensions.default" or something like that.

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: ERXMigrationTable.newColumn does not set default value
      • From: Anjo Krank <email@hidden>
References: 
 >ERXMigrationTable.newColumn does not set default value (From: Helmut Schottmüller <email@hidden>)
 >Re: ERXMigrationTable.newColumn does not set default value (From: Mike Schrag <email@hidden>)
 >Re: ERXMigrationTable.newColumn does not set default value (From: "Mr. Pierre Frisch" <email@hidden>)
 >Re: ERXMigrationTable.newColumn does not set default value (From: Mike Schrag <email@hidden>)
 >Re: ERXMigrationTable.newColumn does not set default value (From: "Mr. Pierre Frisch" <email@hidden>)

  • Prev by Date: Re: unit tests and woapplication bundles, resources, etc.
  • Next by Date: Re: Staying with WebObjects
  • Previous by thread: Re: ERXMigrationTable.newColumn does not set default value
  • Next by thread: Re: ERXMigrationTable.newColumn does not set default value
  • Index(es):
    • Date
    • Thread