Klaus said:
Has anyone in her got experience with O/R Mappers for dotnet?
Some of the requiriments could be
-Enterprise level
we have a lot of enterprise level users, and a lot of systems have
been made with LLBLGen Pro which have 500 tables/views or more (some
even 2500+ tables)
Caching can be 'nice' but remember that caching is often not worth the
effort, for a couple of reasons:
- only in single entity fetches a cache can help you. If you fetch a
set of entities, you first always have to consult the persistent
storage, then pull in the entities not already in the cache, or refresh
the entities already in the cache. this is often slower.
- .NET doesn't have cross-appdomain object awareness. This means that
if your application works on a webfarm/ server farm, your code will
have to consult an external cache system, to be sure the objects are in
a cache or not. This means that this is AND slower, AND you effectively
re-do what's already build into every normal RDBMS: data cache.
Our code is very stable and mature (live since sept 2003). We also use
a policy where fixes have to be released a.s.a.p. so if a customer
reports an issue, a fix is available soon thereafter so you never have
to wait a long time for a service pack or quaterly roll up.
We support oracle 8i-10g through ODP.NET.
Frans
--