Re: EOPrototype help

The new frameworks each have only a single entity, EOJDBCPrototypes --  
not the entire model.  Add one db specific prototype framework and one 
db agnostic entity model (with NO EOJDBCPrototypes entity in it!) to 
your app's classpath and you are set.

Chuck


On Jan 4, 2005, at 12:34 PM, Simeon Johnston wrote:

> While I would love to get that book, I don't think it's possible at 
> this time...
> I also can't find anything on either of those sites.  Lot's of stuff 
> for changing the connection dictionary and modifying just about 
> everything else.
> Nothing for prototypes though (not yet anyway, still looking).
>
> Maybe I just don't understand what the separate framework is for, but 
> it seems a bit much for what were doing.  The database structure will 
> be exactly the same no matter what DBMS is used.
> All I need is a separate prototype for each database, using the same 
> eomodel file.  That is what the extra framework is for right?
> But why create a completely new framework when all I need to do is 
> replace the EOJDBCPrototypes when the model is loaded.
>
> It just seems easier and less prone to programming and packaging error 
> to me.  Maybe one plist file for each different database that is 
> packaged with my existing model framework or just do it right in the 
> code.
>
> sim
>
> On Jan 4, 2005, at 12:33 PM, Chuck Hill wrote:
>
>> I prefer the seperate framework.  If you look on www.wocode.com or
>> www.wodev.com, I'm pretty sure there is code showing how to build the
>> prototypes entity at runtime.  Of, of course, see Practical WebObjects
>> starting on page 47.
>>
>> Chuck
>>
>> At 12:07 PM 04/01/2005 -0600, Simeon Johnston wrote:
>>> I have an application that was build on FrontBase and I am trying to
>>> make it work with Postgresql as well.  Using the same eomodel file.
>>>
>>> As near as I can tell I need to mess with the EOJDBCPrototypes from 
>>> our
>>> current eomodel file and adjust them for Postgresql.
>>>
>>> SO...
>>> Existing eomodel file uses EOJDBCPrototypes for all entity 
>>> attributes.
>>> The prototypes only define the Value Class, External Type and Width
>>> where applicable.
>>>
>>> What I'd like to do is override the EOJDBCPrototypes at application
>>> startup, depending on which database is being used for that 
>>> particular
>>> instance of the application.
>>>
>>> This is where I get lost.  I can't seem to find any documentation 
>>> about
>>> how to override this (in the WO 5.2.3 documentation, google search,
>>> omnigroup etc.).
>>>
>>> I found something about creating a separate framework with your
>>> prototype and change the framework you use for each database...  
>>> seems
>>> a bit much to me.
>>> I see in the documentation that I could, if I wanted to, create the
>>> whole eomodel in code.  That leads me to believe that I should be 
>>> able
>>> to create (or at least set) the prototype that is being used 
>>> depending
>>> on which database is being used.
>>>
>>> Except I can't figure out where to do that...
>>>
>>> sim
>>>
>>> _______________________________________________
>>> EOF mailing list
>>> [email protected]
>>> http://www.omnigroup.com/mailman/listinfo/eof
>>>
>>
>> --
>>
>> Chuck Hill                                 [email protected]
>> Global Village Consulting Inc.             
>> http://www.global-village.net
>> _______________________________________________
>> EOF mailing list
>> [email protected]
>> http://www.omnigroup.com/mailman/listinfo/eof
>>
>
> _______________________________________________
> EOF mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/eof
>
-- 
Practical WebObjects - a book for intermediate WebObjects developers 
who want to increase their overall knowledge of WebObjects, or those 
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects