Cache management in Torque 3.1

[Ra...@gsk.com]

Does cache management work in Torque 3.1?
What does it actually do for you? does it do write-through on updates? Are
there any changes needed to user-level code?
How do you configure it? Is it just setting  'useCache=true' in
torque.properties or do you need to do more?
Does it require any extra jars that are not part of the standard torque
distiribution?




---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

Re: MySQL and autoincrement

[Don Vawter <do...@vawter.com>]

nevermind. attribute is autoIncrement not autoincrement

Don Vawter wrote:

> If I set the idmethod to native and add the attribute  
> autoincrement="true" to my primary key columns I expected them to be 
> autoincremented in MySql. They aren't. Looking at the generated sql 
> reveals that nothing about autoincrement exists.
>
> What I do now is edit the sql file before running it but it doesn't 
> seem like that is the best approach :-) because the changes are lost 
> if I modify the schema.
>
> Suggestions?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

MySQL and autoincrement

[Don Vawter <do...@vawter.com>]

If I set the idmethod to native and add the attribute  
autoincrement="true" to my primary key columns I expected them to be 
autoincremented in MySql. They aren't. Looking at the generated sql 
reveals that nothing about autoincrement exists.

What I do now is edit the sql file before running it but it doesn't seem 
like that is the best approach :-) because the changes are lost if I 
modify the schema.

Suggestions?



---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

Updating To Torque 3.1.1-rc2 caused turbineservlet error

[al...@bapepam.go.id]

I recently try to update my application from using torque-3.1.jar
to the latest torque 3.1.1-rc2.jar and expecting the correct behaviour
in postgres bit handling. But i don't know why my turbine servlet throw a 
null pointer exception while initializing the runtimeservice.
Any changes in torque-3.1.1 config to enable it work correctly with my 
turbine based apps? 

 

Best Regards, 

Albert 

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org