> > > Are we using torque to generate the peer/map classes for
> > > Turbine itself?
> >
> > Nope.
>
> Ok, roughly what would it take to move there?
You'll probably have to build support into Torque to be able to handle the
Hashtable persisted to a blob field for getPerm/setPerm. You'll also need
to look at the fact that getPerm/setPerm automatically looks for a field in
the dbMap with the same name before falling back to the Hashtable.
I think that if this is in place we'll be more that halfway there....
> We are extending Turbine's map builder with our own, and
> I'm trying to figure out the best way to do it and reuse
> most of the code.
>
This worked fine for me:
public class MyMapBuilder extends TurbineMapBuilder
{
public void doBuild() throws Exception
{
super.doBuild();
TableMap tMap = dbMap.getTable(getTableUser());
tMap.addColumn("MY_STRING", "");
}
}
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
