Beautiful! Thanks, Mike!
Richard Palmer
On Sep 15, 2006, at 2:06 PM, Mike Schrag wrote:
> Database Configs (as you have created with the New Database Config
> icon) are used:
>
> 1) during SQL generation (you will be presented with a pulldown)
> 2) at runtime when you use Project Wonder, by specifying
> modelName.DBConfigName=MySqlConfig in your properties
>
> Currently we still only use the primary Connection Dictionary
> definition to determine the prototypes to pull, and it has to
> actually "guess" . Right now the logic it uses to guess prototypes
> is that it will look for PlugIn name first (if you set it in your
> connection dictionary), and try to load
> EOJDBC<pluginname>Prototypes. Next it will try to parse your JDBC
> connection string and look for
> EOJDBC<nameofyouradaptor>Prototypes. Note that #2 there is case
> sensitive, so if you use jdbc:mysql vs jdbc:Mysql that makes a
> difference, although setting plugin might be the better option for
> now.
>
> My proposal going forward, however, is to switch EM to ONLY use
> Database Configs. When a model is loaded in, it will automatically
> create a database config that is your connection dictionary. This
> will allow you to explicitly choose the prototype to use for the
> default config. Additionally, there will be an option to select a
> database config and "make database config active" which will then
> become 1) the connection dictionary that gets written out as the
> default and 2) the one used inside of EM to show you your
> prototypes. This, I believe, really unifies the concepts together
> nicely and essentially makes the "old way" (conn dictionary) just a
> compatibility element rather than a real dependency.
>
> ms
>
> On Sep 15, 2006, at 1:45 PM, Richard Palmer wrote:
>
>> Kieran's very helpful blog was one of the many things I looked
>> at, but it doesn't really address my question which probably is
>> not well posed.
>>
>> Am I wrong in thinking that can dynamically change database
>> connections in Entity Modeler with the New Database Icon?
>> This sets up something like the following in the index.eomeld
>> userinfo:
>>
>> databaseConfigs =
>> {
>> MySqlConfig =
>> {
>> connectionDictionary =
>> {
>> password = foobar;
>> URL = jdbc:mysql://dapper.gs.net/mydb;
>> username = rdp;
>> };
>> prototypeEntityName = EOJDBCMysqlPrototypes;
>> };
>> OpenBaseConfig =
>> {
>> connectionDictionary =
>> {
>> URL = jdbc:openbase://127.0.0.1/MedicalMan;
>> };
>> prototypeEntityName = EOJDBCOpenBasePrototypes;
>> };
>> };
>>
>> How do I get an entity to glom onto one of these settings, e.g.
>> MySqlConfig.
>>
>> Richard Palmer
>>
>> On Sep 15, 2006, at 11:55 AM, Kieran Kelleher wrote:
>>
>>> "Setting up ERPrototypes"
>>> http://homepage.mac.com/kelleherk/iblog/C183784902/E490825431/
>>> index.html
>>>
>>> On Sep 15, 2006, at 12:03 PM, Richard Palmer wrote:
>>>
>>>> What is the secret to using ERPrototypes in Entity Modeler?
>>>>
>>>> I set up an SQL Config with a connection dictionary and choice
>>>> of prototypes from the ERPrototypes framework in the outline
>>>> view, but how do I get the Entities and Attributes to use this
>>>> Config? My attributes Basic view all have 'No Prototype' in
>>>> the Prototype chooser.
>>>>
>>>> Richard Palmer
>>>
>>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Fri Sep 15 2006 - 18:00:08 EDT