|Re: DB Persistence [message #699277 is a reply to message #699184]
||Thu, 21 July 2011 08:10
Originally posted by: Jonas Helming|
EMFStore has a abstract persistence layer, the default implementation is
XMI. 2 years ago, we had an implementation for DB based on Teneo. We
discovered, that due to the kind of read/write operations on the server
XMI was faster than the DB implementation. The server mostyl stores data
and quite seldom reads it again, mainly only if you access the history.
As a disadvantage, a DB back-end makes the model migration much more
complicated. If DB storage is required, that is definitly possible to
implement. Could you open a bug report in this case, to discuss this?
Am 21.07.2011 05:13, schrieb Mike Haney:
> We have been evaluating EMFStore and it seems to fulfill most of our
> requirements for our new model-driven application platform. The only
> thing missing that I know will be a requirement for some projects is DB
> persistence. Many of our large enterprise customers would balk at
> storing their data as XML files somewhere on the server, so some type of
> ORM is definitely needed.
> I noticed in the proposal document that it said the server could use
> EclipseLink for persistence, but I can't find any documentation on how
> to do this. Is this feature not implemented yet, or merely not
> documented yet?
Powered by FUDForum
. Page generated in 0.02486 seconds