Mon Oct 07 05:21:31 GMT 2013
From
/weblog/database/objective
A presentation about Politics issues of using ORM persistence -
http://www.softwaresummit.com[..]ers/SmithDonaldPoliticsOfPersistence.pdf A checklist of features of ORM library, which, I think, may be too detail to consider that much?
http://madgeek.com/Articles/ORMapping/EN/mapping.htm Some problem of ORM nowadays -
http://blogs.ittoolbox.com[..]e-ubiquitous-bastardization-of-orm-17100 This post rise a good point, if the ORM tool doesn't provide a simpler solution, why bother to use it? Just because many people using it?
http://en.newinstance.it/2006/10/23/trimming-jdbc/ We have been using hibernate for while, actually it is good. But LGPL block us from using it anymore...
Here is some other experience about this -
http://shinetech.com/pages/viewpage.action?pageId=649 and the discussion of this article -
http://www.theserverside.com[..]m/news/thread.tss?thread_id=41174#212825 Some interestig ORM packages without XML
http://www.jenkov.com/mrpersister/introduction.tmpl http://www.simpleorm.org/sorm/whitepaper.html http://www.h2database.com/html/jaqu.html And there is one try to use javadoc doclet approach to make all those SQL documented at javadoc also, look like an interesting idea -
http://voruta.sourceforge.net/ Advantage of using ORM, but are those really so important?
http://ayende.com[..]oWriteYourOwnObjectRelationalMapper.aspx Good source about various pattern and test on ORM -
http://blog.xebia.com/category/jpa/implementation-patterns/ Analysis on ORM package -
http://seldo.com/weblog/2011/06/15/orm_is_an_antipattern
(google search)
(amazon search)
Mon Mar 17 17:25:23 GMT 2008
From
/weblog/database/objective
A nice article which talk about relation DB and OO. But I have an difference opinions, I think that advantage of relational database is the problem that OO like to prevent.
The main advantage of relational database is the relatioal model make it easy to perform reporting. However, relation model is more difficult than hierarchical model (OO model) to enable encapsulation and polymorphism.
Turn out, if we stand on OO programmer point of view, we will complaint that most RDBMS is in fact just a giant global variable; If we stand as DBA point of view, we will complaint other thing.
Can we create something that optimize for both world? I don’t think so…
http://jooto.com/blog/index.php/2005/11/17/databases-and-objects/ Update: a message also discuss about this:
http://groups.yahoo.com/group/pragprog/message/5682 Update #2: A further analysis of ORM:
http://www.codinghorror.com/blog/archives/000621.html
(google search)
(amazon search)
Thu Oct 12 09:33:03 GMT 2006
From
/weblog/database/objective
Transparent Persistence is a marketing term (that means "lie"), it isn't. However, because you need to spend far less effort on persistence you tend to really want it to be true, and code as if it is.
...
Probably, what we all need to do, is to remove the word "transparent" from "transparent o/r mapping" and admit that it is simply a high level tool, be up front about the design considerations, and talk a lot more about how to design applications using these tools rather than what the tools can do.
http://kasparov.skife.org/blog/src/objects-wars-tb.writeback
(google search)
(amazon search)