+972 52-548-6969
How many digs in a single paragraph?
time to read 1 min | 178 words
From the Hibernate Blog:
Well, it is nice for us, but it's not nice for the guy who comes along next! He's one of those shiny-eyed (and slightly scary) Ruby fanatics. Or maybe he's a VB guy (senior citizens matter too). Or maybe its 5000 years from now: Java and Ruby have both vanished (of course, VB is going strong) and a team of archeaologists from Ganymede are trying to piece together something about our forgotten civilization from what's left of your customer database, using the recently released Perl 6.0. Wouldn't it be easier for them if your database just had strings and numbers in it?
You really have to read the whole thing to get the spirit of the thing. ROTFL.
Oh, and the message isn't that bad either, I had similar discussion with Ted Neward on the OR/M Smackdown.
Comments
It's Hibernate, not Hiberante ;-) And actually, I think it was published somewhere before, even though Gavin says it wasn't.
Hiberante <-> Hibernate just as long as the bear is asleep, I don't care how he spells it.
fixed, thanks.
Since I can't respond there I will respond here. This statement is incorrect from the rant:
"However, I will concede that there is a particular case where current relational technology is inferior: fetching of arbitrarily deep graphs of data in a hierarchical relationship."
http://www.codeproject.com/cs/database/Trees_in_SQL_databases.asp
I have found that creating specialized node path tracking reference tables with the correct indexing can perform very well.
Also you can use the left, right region markers on your nodes to allow indexed based set operations.
Both of these techniques do not utilize special vendor extensions. (btw, I really like SQL '05 CTEs these days)
Of course neither of these techniques address high performance node movements but that was not the statement that was made.
Does NHibernate have any support for recursive retrieval of hierarchical represented data? Is this simply the use of a lazy load? (Please excuse my lack of NHibernate xp)
@Mark,
Read the rest of the statement, it acknowledge that there are propriety ways to do hierarchical queries, but that it is vendor specific, so not really a good fit for Hibernate.
Another problem is that hierarchical queries doesn't necessarily mean a hierarchy such as in a tree, but getting Blog->Posts->Comments.
I would assert that relational technology is superior for performing arbitrarily deep graphs of data in a hierarchical relationship without vendor specific technology though the use of correct indexing support.
Are you saying hierarchy is not a tree? A tree (directed graph) is a data structure used to implement the general concept of hierarchy. You lost me there.
Comment preview