Larry,
Thanks for the reply. But I am not so sure about it.
Anyway, i am exploring the option of using rowhandler. Lets see if i can use
it effectively.
--
View this message in context:
http://www.nabble.com/Help-needed-for-representing-complex-business-relationship-tf4574170.html#a13090220
Sent
I've replied to Brandon since this is off topic for this list.
Brandon Goodin wrote:
Why not just create an ImageSizes table? The ImageSizes
table would contain | id | imageId | width | height | sizeKey |
Then you have a 1 to many relationship with your Image and you can use
queryForMap an
Why not just create an ImageSizes table? The ImageSizes table would contain
| id | imageId | width | height | sizeKey |
Then you have a 1 to many relationship with your Image and you can use
queryForMap and make the sizeKey (which could be size1, size2, size3,
size4...) the key of the Map.
Additi