Using prototypes with more than one EOModel and different databases

Hi,

I   have  two  EOModels  in  a  project  that  are  used  to  maintain
user-specific  and  content-specific  data.  In  one EOModel I have an
'EOPrototypes' entity that contains all prototypes for both models.

Both  models  now  connect  to the same database but in the future, it
should  be  possible to connect to two different databases (say, mySQL
and  FrontBase).  Has anyone tried this and can tell how to handle the
prototypes  thingy  then?  Changing the connection dictionary is not a
problem,  it  is  the  external  types (varchar vs. TEXT) that I worry
about.

I have a few guesses but wanted to ask first before reinventing the
wheel:

1. It does not work. Stick with one database server. My idea for now.

2. Have one EOPrototype entity per EOModel. Might not work because of
   a naming conflict in the EOModelGroup later.

3. Have separate EOModelGroups, each with one model. Might not work
   with WO because it loves its defaultModelGroup best.

4. Another cool solution I have not seen yet...

-- 
Regards,
 Stefan