[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

[timfox]

"ovidiu.feodorov at jboss.com" wrote : 
  | Keeping information like "destination" in its own main table field will speed up queries, isn't it? Otherwise, you'll need to use a JOIN instead of a simple SELECT.
  | 

Destination is never used in queries. The core joins on channel id only (you can think of this as the real core destination) which is in it's own column.


anonymous wrote : 
  | Stuffing non-generic information as message headers will impact performance. It's difficult to say how much, without proper measuring, though.
  | 

Not so. I wouldn't have suggested it, if that was the case.


anonymous wrote : 
  | This is what migration utilities are for. We won't have to live forever with it, we will just have to go through the trouble of writing a migration tool. We need to do this while migrating from 1.0 to 1.2 anyway.
  | 

We don't need this for 1.2 since we have specifically said no compatibility until after 1.2. This is why it needs to be done now.

anonymous wrote : 
  | Personally, I don't believe in the "perfect generic design" that "fits every possible case". We need to have a plan for evolution, not perfection, which is unattainable.
  | 

Who said it was a perfect gerneric design? It is just a better design than before. An "evolution" in your words.

And please, we don't have weeks to debate this.......

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011807#4011807

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011807