Tim wrote : | As part of http://jira.jboss.com/jira/browse/JBMESSAGING-739 I am considering removing those columns and just storing those values as core headers in the message. | | E.g. there would be a core header called JBM.JMS.Destination (or whatever), which had destination as its value. | 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. Stuffing non-generic information as message headers will impact performance. It's difficult to say how much, without proper measuring, though. Tim wrote : | I don't want to be in a situation where we end up with a crappy schema we have to live with for ever. | 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. 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. Could you please jot down the schema, as you think it should be, before going ahead and changing code? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011700#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...