Hi John,
----- Original Message -----
From: John McNally <[EMAIL PROTECTED]>
> I don't think it matters how many MapBuilders you have. I guess when I
> think of a DatabaseMap, I assume there is one DatabaseMap per database. I
> do not see the reason to have multiple DatabaseMaps per database, though
> maybe there is a good reason. Are people creating multiple TableMaps per
> table with each one only containing some of the columns in the table?
The only reason why I do this is to keep the TurbineMapBuilder in tact. I don't want
to mess with code that is already
working and I feel that this is almost a "standalone unit" which should be re-used for
all apps. For each app I then create
the application specific tables and an application specific MapBuilder. Because id
generation is part of the "Turbine
service" I'd like to use the Turbine MapBuilder but generate id's for tables for the
application specific tables.
Am I trying to force a square into a circle by doing this with the id broker?
Copy/Paste TurbineMapBuilder code for each
new application doesn't ring right to me though :-) Could you maybe explain to me how
you are using this at the moment - I
think I'm missing the point...
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
