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 ja
Up to now I have assumed that things work as you explained. However opening
new connections is typically a fairly slow business. When programming in C
or Perl one gets used to using the same connection over and over again,
processing transactions in a loop. This does not appear to be possible with
So you are saying that one cannot do more than one transaction with a
connection. Surely commit/rollback is a separate matter from saying, 'I
have finished with this connections, now let someone else use it'?
Of course, I can close the connection, which will force the pool manager to
create a new
A bit of clarification please.
One uses torque.getConnection to get a DB connection from the pool. How and
when is it returned to the pool?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PR
I'm not sure whether this should go into the tutorial, the reference docs
or the WIKI.
It is possible to add any attribute you like to the schema XML; it will be
ignored by the generator scripts. I find this useful in order to add extra
semantics to the schema, which I then pick up in my own xml p
Hvae you looked at java.util.Collections? See the methods reverse(), which
reverses (moodifes) the collection, and reverseOrder(), which just provides
a convenient comparator.
Try something like
// Create a TreeMap that sorts in the reverse order
SortedMap sortedMap = ne
It is frequently not quite what is wanted. For instance, I want to find all
orphaned objects, so I need to construct a Criteria that is equivalent to
WHERE id NOT IN (SELECT id FROM othertable)
and to use this in a doSelect() or doDelete(). I do not want to construct
an SQL statement by han
Thank you.
I already have a patched village*.jar that enables me to store and
retrieve timestamps without truncation. However AFAICT it also does not
truncate dates, which is not in accordance with ANSI.
I believe that we still need a change to the templates or libraries so that
timetamps are st
I have found a hole in the validation of the schema XML.
I used to have a column FORMULAID, which I removed. However there was
still a UNIQUE constraint for it in the schema. This was inconsistency was
not detected by the ant 'sql' task and was picked up ony when I tried to
run the generated DDL.
My second problem is also a bit of a nuisance. i.e. that the value returned
by Torque is a java.sql.Timestamp (or java.sql.Date) whereas the data
fields are declared as java.util.Date. This causes things to go wrong later
because neither of these returned types is really a semantic sub-type of
java
I am using Torque 3.1 with an Oracle DB. I am trying to create tables that
have date/time fields. I find that it makes absolutely no difference
whether in the xml I declare the columns as DATE or TIMESTAMP; the DDL and
code generated are exactly the same. The effect of this is that the time
compo
11 matches
Mail list logo
