• 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: Framework EOModel Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework EOModel Question


  • Subject: Re: Framework EOModel Question
  • From: Anjo Krank <email@hidden>
  • Date: Fri, 5 Aug 2005 10:06:19 +0200

Am 05.08.2005 um 09:53 schrieb LD:
Okay, I'm sold on Project Wonder - too many "Oh, and PW does that already..." :-)
I need a bit more time before I can spend enough time to grapple with an additional setup...

Take your time :)

However, I'd advise prototypes only when you have either only one model or are very disciplined:

I've using 4 simple models. I can see the benefits even with my simple list of entities. The annoying thing, however, is with EOModeler. i.e., if I define some prototypes with properties for value type, value class, allowsNull etc but _without_ a column name - then when I assign that prototype to an attribute that already has a column name the silly thing will remove the column name after you close the model.

Which is part of what I meant. There are a lot of other quirks, too, most of which I forgot as we now have our own prototypes handling (one that actually works:)


Hence the use of the PostgresqlPlugIn.framework. Works well (with my slight alteration to the plugin).

What "alterations"?

The alteration was to the HexDreams 1.2 version (see below [1]). Now, you're going to tell me that Project Wonder already has a better postgresql plugin. It's okay - you can say it ;-)

[snip code]

Well... I don't know what the rationale is behind that fragment, but in the worst case, you get three additional DB roundtrips *per insert*. I'd rather make it so the serial's name is in the entities or PKs userInfo and it will choose that instead of trying the names nilly-willy... or you do it your way and set the value in the userInfo after the first discovery.

If you make a patch to the Wonder plugin (which is of course much better, shiny and brighter:), I'll see that I can integrate it.

Cheers, Anjo
_______________________________________________
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: Framework EOModel Question
      • From: LD <email@hidden>
    • Re: Framework EOModel Question
      • From: Mike Schrag <email@hidden>
References: 
 >Re: Framework EOModel Question (From: LD <email@hidden>)
 >Re: Framework EOModel Question (From: Chuck Hill <email@hidden>)
 >Re: Framework EOModel Question (From: LD <email@hidden>)
 >Re: Framework EOModel Question (From: Chuck Hill <email@hidden>)
 >Re: Framework EOModel Question (From: LD <email@hidden>)
 >Re: Framework EOModel Question (From: Chuck Hill <email@hidden>)
 >Re: Framework EOModel Question (From: Anjo Krank <email@hidden>)
 >Re: Framework EOModel Question (From: LD <email@hidden>)

  • Prev by Date: Re: Framework EOModel Question
  • Next by Date: Re: Framework EOModel Question
  • Previous by thread: Re: Framework EOModel Question
  • Next by thread: Re: Framework EOModel Question
  • Index(es):
    • Date
    • Thread