Book a Demo

Author Topic: Database selector needed in Package  (Read 5591 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Database selector needed in Package
« on: August 23, 2007, 05:19:05 pm »
An EA Package allows you to select a coding language.  It's not clear from the documentation I could find whether this value is actually used currently by EA.  However, it could be useful to user created add-ins.

Notwithstanding that, at this level of model, a database selector is also needed.  Please provide one.

Paolo
[size=0]©2007 Paolo Cantoni, -Semantica-[/size]
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

thomaskilian

  • Guest
Re: Database selector needed in Package
« Reply #1 on: August 23, 2007, 10:39:17 pm »
I guess it's used as default for the classes created therein.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Database selector needed in Package
« Reply #2 on: August 24, 2007, 02:42:24 am »
Got it in one Paolo!

Add another vote.
No, you can't have it!

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: Database selector needed in Package
« Reply #3 on: August 26, 2007, 10:37:23 am »
Count me in.

Large enterprise systems often need to bridge multiple legacy DBMS'.
Verbal Use Cases aren't worth the paper they are written upon.

dbax

  • EA User
  • **
  • Posts: 69
  • Karma: +0/-0
  • One EA To Rule Them All
    • View Profile
Re: Database selector needed in Package
« Reply #4 on: August 27, 2007, 03:22:54 pm »
Add my vote too! I am also involved in Enterprise-wide architecture where multiple DBMS are used and will continue to be. Having something like this would definitely benefit my projects.