You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by Ivan Ivankovic <iv...@pamet.co.yu> on 2006/11/16 18:42:28 UTC
Cache problem after delete
Hi,
I worked with Torque only for past 2 weeks, and I found it very useful.
I use Torque 3.0 with Postgres and have following problem:
After deleting some concrete object with usual
ClassNamePeer.doDelete(objectToDelete), I can still see it in database when
querying for that objects information with plain JDBC.
When I use any of Torque query methods, via Criteria or retrieveByPK(key),
object seems to be erased, but some parts of application I am working on use
JDBC so I can't rewrite all code to use Torque
BasePeer.executeQuery(queryString). Database data for this object can also
be seen from Squirrel JDBC browser which of course uses plain JDBC.
I suppose that Torque has some delayed deletion mechanism and I need some
way to make him do the actual deletion completely from database. Is there
some kind of "flush" to achieve this?
Regards,
Ivanko
RE: Cache problem after delete
Posted by Ivan Ivankovic <iv...@pamet.co.yu>.
Thanks Thomas and all of you guys. I see you understood my problem and last
post from Thomas seems to be the answer.
If I experience some more problems with Torque 3.2 be sure I will let you
now :)
Thanks again!
Ivanko
-----Original Message-----
From: Thomas Fischer [mailto:tfischer@apache.org]
Sent: Saturday, November 18, 2006 2:24 PM
To: Apache Torque Users List
Subject: RE: Cache problem after delete
Ivan,
this really sounds as if the transaction in which you delete the data sets
is not closed: If you use the same conection to re-read the data (with
Torque), the datasets are gone, but if you use another connections, the
datasets are still there because the transaction where the delete occurred
is not yet committed.
Maybe Torque 3.0 had a problem with transaction handling. Back then,
transactions were not supported by most open source databases, so errors
might not have been noticed.
I can see two options for you:
- Upgrade to a newer Torque version
- debug the code yourself and find out why the transaction si not closed.
Hope that helps,
Thomas
On Fri, 17 Nov 2006, Ivan Ivankovic wrote:
>
> Hi Michel,
>
> I already tried to wrap deletion in transaction and it didn't work but the
> thing you're saying about table locks might be the answer. Could you
explain
> me hoe to check those locks?
>
> Program flow where I first encountered this problem goes like this:
>
> 1. User is provided with list of database records on web page. Every one
of
> them has delete button beside. List is obtained with JDBC query.
>
> 2. After clicking delete in Struts action deletion is done with Torque,
and
> user is forwarded back to list page.
>
> 3. JDBC query is performed in order to redisplay list. And guess what :)
> data I've just deleted is still there. It is in database when I check with
> Squirrel DB browser as well.
>
> Solution 1: When I rewrote list action to use Torque instead of JDBC data
is
> gone for good. I checked it with DB Browser and it also isn't here.
>
> Solution 2: When I delete data with Torque I ask for it again with Torque
> with retrieveByPK(key). I caught exception thrown because Torque didn't
find
> data and forward to list page. List uses JDBC but data is now gone.
>
> That made me think that actually invalidation is performed instead of
> deletion; and real deletion happens after data is first read. With Torque
of
> course.
>
> Can you help me with those locks maybe that the will help.
>
> Thanks,
> Ivanko
>
> -----Original Message-----
> From: Michael Manske [mailto:netseeker@manskes.de]
> Sent: Thursday, November 16, 2006 8:33 PM
> To: Apache Torque Users List
> Subject: Re: Cache problem after delete
>
> Hi Ivan,
>
> > I use Torque 3.0 with Postgres and have following problem:
> 3.0 is a little bit out-dated, isn't it? ;-)
>
> > After deleting some concrete object with usual
> > ClassNamePeer.doDelete(objectToDelete), I can still see it in database
> when
> > querying for that objects information with plain JDBC.
> That should not happen, as long as you don't use
>
> Connection con = Transaction.begin("myDB");
> ClassNamePeer.doDelete(objectToDelete, con);
>
> and did not commit the transaction via
>
> Transaction.commit(con);
>
> > I suppose that Torque has some delayed deletion mechanism
> No, Torque has not such a mechanism - the record should be deleted
> immediately as long as no other process holds a lock on the record or
table.
> Checking for locks on the table could be a good idea. We were facing
> a similiar behaviour with Oracle some time ago:
> While using the doDelete() and doUpdate() methods, sometimes it took long
> time
> until Oracle told the client that it has detected a lock. Perhaps you are
> facing a similiar situation with Postgres?
>
> cheers
> Michael
>
> Ivan Ivankovic schrieb:
>> Hi,
>>
>>
>>
>> I worked with Torque only for past 2 weeks, and I found it very useful.
>>
>>
>>
>> I use Torque 3.0 with Postgres and have following problem:
>>
>> After deleting some concrete object with usual
>> ClassNamePeer.doDelete(objectToDelete), I can still see it in database
> when
>> querying for that objects information with plain JDBC.
>>
>>
>>
>> When I use any of Torque query methods, via Criteria or
retrieveByPK(key),
>> object seems to be erased, but some parts of application I am working on
> use
>> JDBC so I can't rewrite all code to use Torque
>> BasePeer.executeQuery(queryString). Database data for this object can
also
>> be seen from Squirrel JDBC browser which of course uses plain JDBC.
>>
>>
>>
>> I suppose that Torque has some delayed deletion mechanism and I need some
>> way to make him do the actual deletion completely from database. Is there
>> some kind of "flush" to achieve this?
>>
>>
>>
>> Regards,
>>
>> Ivanko
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.0.409 / Virus Database: 268.14.6/535 - Release Date:
15.11.2006
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.409 / Virus Database: 268.14.6/535 - Release Date: 11/15/2006
>
>
>
> ---------------------------------------------------------------------
> 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
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.6/536 - Release Date: 11/16/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
RE: Cache problem after delete
Posted by Thomas Fischer <tf...@apache.org>.
Ivan,
this really sounds as if the transaction in which you delete the data sets
is not closed: If you use the same conection to re-read the data (with
Torque), the datasets are gone, but if you use another connections, the
datasets are still there because the transaction where the delete occurred
is not yet committed.
Maybe Torque 3.0 had a problem with transaction handling. Back then,
transactions were not supported by most open source databases, so errors
might not have been noticed.
I can see two options for you:
- Upgrade to a newer Torque version
- debug the code yourself and find out why the transaction si not closed.
Hope that helps,
Thomas
On Fri, 17 Nov 2006, Ivan Ivankovic wrote:
>
> Hi Michel,
>
> I already tried to wrap deletion in transaction and it didn't work but the
> thing you're saying about table locks might be the answer. Could you explain
> me hoe to check those locks?
>
> Program flow where I first encountered this problem goes like this:
>
> 1. User is provided with list of database records on web page. Every one of
> them has delete button beside. List is obtained with JDBC query.
>
> 2. After clicking delete in Struts action deletion is done with Torque, and
> user is forwarded back to list page.
>
> 3. JDBC query is performed in order to redisplay list. And guess what :)
> data I've just deleted is still there. It is in database when I check with
> Squirrel DB browser as well.
>
> Solution 1: When I rewrote list action to use Torque instead of JDBC data is
> gone for good. I checked it with DB Browser and it also isn't here.
>
> Solution 2: When I delete data with Torque I ask for it again with Torque
> with retrieveByPK(key). I caught exception thrown because Torque didn't find
> data and forward to list page. List uses JDBC but data is now gone.
>
> That made me think that actually invalidation is performed instead of
> deletion; and real deletion happens after data is first read. With Torque of
> course.
>
> Can you help me with those locks maybe that the will help.
>
> Thanks,
> Ivanko
>
> -----Original Message-----
> From: Michael Manske [mailto:netseeker@manskes.de]
> Sent: Thursday, November 16, 2006 8:33 PM
> To: Apache Torque Users List
> Subject: Re: Cache problem after delete
>
> Hi Ivan,
>
> > I use Torque 3.0 with Postgres and have following problem:
> 3.0 is a little bit out-dated, isn't it? ;-)
>
> > After deleting some concrete object with usual
> > ClassNamePeer.doDelete(objectToDelete), I can still see it in database
> when
> > querying for that objects information with plain JDBC.
> That should not happen, as long as you don't use
>
> Connection con = Transaction.begin("myDB");
> ClassNamePeer.doDelete(objectToDelete, con);
>
> and did not commit the transaction via
>
> Transaction.commit(con);
>
> > I suppose that Torque has some delayed deletion mechanism
> No, Torque has not such a mechanism - the record should be deleted
> immediately as long as no other process holds a lock on the record or table.
> Checking for locks on the table could be a good idea. We were facing
> a similiar behaviour with Oracle some time ago:
> While using the doDelete() and doUpdate() methods, sometimes it took long
> time
> until Oracle told the client that it has detected a lock. Perhaps you are
> facing a similiar situation with Postgres?
>
> cheers
> Michael
>
> Ivan Ivankovic schrieb:
>> Hi,
>>
>>
>>
>> I worked with Torque only for past 2 weeks, and I found it very useful.
>>
>>
>>
>> I use Torque 3.0 with Postgres and have following problem:
>>
>> After deleting some concrete object with usual
>> ClassNamePeer.doDelete(objectToDelete), I can still see it in database
> when
>> querying for that objects information with plain JDBC.
>>
>>
>>
>> When I use any of Torque query methods, via Criteria or retrieveByPK(key),
>> object seems to be erased, but some parts of application I am working on
> use
>> JDBC so I can't rewrite all code to use Torque
>> BasePeer.executeQuery(queryString). Database data for this object can also
>> be seen from Squirrel JDBC browser which of course uses plain JDBC.
>>
>>
>>
>> I suppose that Torque has some delayed deletion mechanism and I need some
>> way to make him do the actual deletion completely from database. Is there
>> some kind of "flush" to achieve this?
>>
>>
>>
>> Regards,
>>
>> Ivanko
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> No virus found in this incoming message.
>> Checked by AVG Free Edition.
>> Version: 7.0.409 / Virus Database: 268.14.6/535 - Release Date: 15.11.2006
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.409 / Virus Database: 268.14.6/535 - Release Date: 11/15/2006
>
>
>
> ---------------------------------------------------------------------
> 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
RE: Cache problem after delete
Posted by Ivan Ivankovic <iv...@pamet.co.yu>.
Hi Michel,
I already tried to wrap deletion in transaction and it didn't work but the
thing you're saying about table locks might be the answer. Could you explain
me hoe to check those locks?
Program flow where I first encountered this problem goes like this:
1. User is provided with list of database records on web page. Every one of
them has delete button beside. List is obtained with JDBC query.
2. After clicking delete in Struts action deletion is done with Torque, and
user is forwarded back to list page.
3. JDBC query is performed in order to redisplay list. And guess what :)
data I've just deleted is still there. It is in database when I check with
Squirrel DB browser as well.
Solution 1: When I rewrote list action to use Torque instead of JDBC data is
gone for good. I checked it with DB Browser and it also isn't here.
Solution 2: When I delete data with Torque I ask for it again with Torque
with retrieveByPK(key). I caught exception thrown because Torque didn't find
data and forward to list page. List uses JDBC but data is now gone.
That made me think that actually invalidation is performed instead of
deletion; and real deletion happens after data is first read. With Torque of
course.
Can you help me with those locks maybe that the will help.
Thanks,
Ivanko
-----Original Message-----
From: Michael Manske [mailto:netseeker@manskes.de]
Sent: Thursday, November 16, 2006 8:33 PM
To: Apache Torque Users List
Subject: Re: Cache problem after delete
Hi Ivan,
> I use Torque 3.0 with Postgres and have following problem:
3.0 is a little bit out-dated, isn't it? ;-)
> After deleting some concrete object with usual
> ClassNamePeer.doDelete(objectToDelete), I can still see it in database
when
> querying for that objects information with plain JDBC.
That should not happen, as long as you don't use
Connection con = Transaction.begin("myDB");
ClassNamePeer.doDelete(objectToDelete, con);
and did not commit the transaction via
Transaction.commit(con);
> I suppose that Torque has some delayed deletion mechanism
No, Torque has not such a mechanism - the record should be deleted
immediately as long as no other process holds a lock on the record or table.
Checking for locks on the table could be a good idea. We were facing
a similiar behaviour with Oracle some time ago:
While using the doDelete() and doUpdate() methods, sometimes it took long
time
until Oracle told the client that it has detected a lock. Perhaps you are
facing a similiar situation with Postgres?
cheers
Michael
Ivan Ivankovic schrieb:
> Hi,
>
>
>
> I worked with Torque only for past 2 weeks, and I found it very useful.
>
>
>
> I use Torque 3.0 with Postgres and have following problem:
>
> After deleting some concrete object with usual
> ClassNamePeer.doDelete(objectToDelete), I can still see it in database
when
> querying for that objects information with plain JDBC.
>
>
>
> When I use any of Torque query methods, via Criteria or retrieveByPK(key),
> object seems to be erased, but some parts of application I am working on
use
> JDBC so I can't rewrite all code to use Torque
> BasePeer.executeQuery(queryString). Database data for this object can also
> be seen from Squirrel JDBC browser which of course uses plain JDBC.
>
>
>
> I suppose that Torque has some delayed deletion mechanism and I need some
> way to make him do the actual deletion completely from database. Is there
> some kind of "flush" to achieve this?
>
>
>
> Regards,
>
> Ivanko
>
>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.0.409 / Virus Database: 268.14.6/535 - Release Date: 15.11.2006
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.6/535 - Release Date: 11/15/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: Cache problem after delete
Posted by Michael Manske <ne...@manskes.de>.
Hi Ivan,
> I use Torque 3.0 with Postgres and have following problem:
3.0 is a little bit out-dated, isn't it? ;-)
> After deleting some concrete object with usual
> ClassNamePeer.doDelete(objectToDelete), I can still see it in database when
> querying for that objects information with plain JDBC.
That should not happen, as long as you don't use
Connection con = Transaction.begin("myDB");
ClassNamePeer.doDelete(objectToDelete, con);
and did not commit the transaction via
Transaction.commit(con);
> I suppose that Torque has some delayed deletion mechanism
No, Torque has not such a mechanism - the record should be deleted
immediately as long as no other process holds a lock on the record or table.
Checking for locks on the table could be a good idea. We were facing
a similiar behaviour with Oracle some time ago:
While using the doDelete() and doUpdate() methods, sometimes it took long time
until Oracle told the client that it has detected a lock. Perhaps you are
facing a similiar situation with Postgres?
cheers
Michael
Ivan Ivankovic schrieb:
> Hi,
>
>
>
> I worked with Torque only for past 2 weeks, and I found it very useful.
>
>
>
> I use Torque 3.0 with Postgres and have following problem:
>
> After deleting some concrete object with usual
> ClassNamePeer.doDelete(objectToDelete), I can still see it in database when
> querying for that objects information with plain JDBC.
>
>
>
> When I use any of Torque query methods, via Criteria or retrieveByPK(key),
> object seems to be erased, but some parts of application I am working on use
> JDBC so I can't rewrite all code to use Torque
> BasePeer.executeQuery(queryString). Database data for this object can also
> be seen from Squirrel JDBC browser which of course uses plain JDBC.
>
>
>
> I suppose that Torque has some delayed deletion mechanism and I need some
> way to make him do the actual deletion completely from database. Is there
> some kind of "flush" to achieve this?
>
>
>
> Regards,
>
> Ivanko
>
>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.0.409 / Virus Database: 268.14.6/535 - Release Date: 15.11.2006
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
RE: Cache problem after delete
Posted by Ivan Ivankovic <iv...@pamet.co.yu>.
Thanks for answering; I already tried Criteria deletion, although my object
and corresponding database table have PK. It didn't work.
JDBC and Torque DB paths are the same.
Torque version is old, but I am programmer not DB administrator so I can't
make migration myself. Sure, after this issue I'll ask for newer Torque.
The thing that's happening here is obviously some delayed deletion. It
reminds me of write-back method used in hardware cache memories (some other
methods use write-through). After writing, data is only invalidated and
first time processor asks for that data real write is done and updated data
is provided back to processor.
Like so, when I ask for deleted object via Torque real deletion happens and
data is not reachable neither by Torque nor JDBC. It is only strange to me
that there is not some "flush" or write-through command to keep Torque and
JDBC in sync.
If you say that Torque doesn't have delay than it could something with
Postgres.
Anyway if you have some more ideas I'll be happy to hear (read) them, while
waiting for newer Torque to be installed.
Regards,
Ivanko
-----Original Message-----
From: Greg Monroe [mailto:Greg.Monroe@DukeCE.com]
Sent: Thursday, November 16, 2006 8:39 PM
To: Apache Torque Users List
Subject: RE: Cache problem after delete
First, I'd suggest upgrading to the latest version of
Torque (3.2 / 3.3 coming soon!) from 3.0. There have
been a lot of things fixed, etc.
Next, Torque does not have a delayed delete mechanism.
When you make the delete call, it does a JDBC delete
call to the DB right then. Note that currently loaded
OM objects are not effect/updated by this. (Other than
the one used to make the delete gets it's isNew() status
updated).
FWIW, it's much safer to delete stuff by using criteria
than objects. If the object does not have a primary key
to identify it, then the delete statement becomes a
based on a concatenation of all the properties. Things
like default values can cause the object not to be found
and deleted. Hmm, any one remember if 3.0 cared about PKs...
I seem to remember it was added later.
Anyway, if your table has primary Keys, try using:
ClassNamePeer.doDelete(deleteObject.getPrimaryKey());
If not, construct an identifying criteria and use this.
Hmm, another thought, based on your Torque can't find it
and JDBC can, is that your Torque.properties setting might
be pointing to a different location than JDBC. E.g.,
development DB for Torque vs JDBC using production DB?
Good luck.
> -----Original Message-----
> From: Ivan Ivankovic [mailto:ivan.ivankovic@pamet.co.yu]
> Sent: Thursday, November 16, 2006 12:42 PM
> To: torque-user@db.apache.org
> Subject: Cache problem after delete
>
> Hi,
>
>
>
> I worked with Torque only for past 2 weeks, and I found it
> very useful.
>
>
>
> I use Torque 3.0 with Postgres and have following problem:
>
> After deleting some concrete object with usual
> ClassNamePeer.doDelete(objectToDelete), I can still see it in
> database when querying for that objects information with plain JDBC.
>
>
>
> When I use any of Torque query methods, via Criteria or
> retrieveByPK(key), object seems to be erased, but some parts
> of application I am working on use JDBC so I can't rewrite
> all code to use Torque BasePeer.executeQuery(queryString).
> Database data for this object can also be seen from Squirrel
> JDBC browser which of course uses plain JDBC.
>
>
>
> I suppose that Torque has some delayed deletion mechanism and
> I need some way to make him do the actual deletion completely
> from database. Is there some kind of "flush" to achieve this?
>
>
>
> Regards,
>
> Ivanko
>
>
Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are
confidential communication or may otherwise be privileged or confidential
and are intended solely for the individual or entity to whom they are
addressed. If you are not the intended recipient you may not rely on the
contents of this email or any attachments, and we ask that you please not
read, copy or retransmit this communication, but reply to the sender and
destroy the email, its contents, and all copies thereof immediately. Any
unauthorized dissemination, distribution or copying of this communication is
strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.14.6/535 - Release Date: 11/15/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
RE: Cache problem after delete
Posted by Greg Monroe <Gr...@DukeCE.com>.
First, I'd suggest upgrading to the latest version of
Torque (3.2 / 3.3 coming soon!) from 3.0. There have
been a lot of things fixed, etc.
Next, Torque does not have a delayed delete mechanism.
When you make the delete call, it does a JDBC delete
call to the DB right then. Note that currently loaded
OM objects are not effect/updated by this. (Other than
the one used to make the delete gets it's isNew() status
updated).
FWIW, it's much safer to delete stuff by using criteria
than objects. If the object does not have a primary key
to identify it, then the delete statement becomes a
based on a concatenation of all the properties. Things
like default values can cause the object not to be found
and deleted. Hmm, any one remember if 3.0 cared about PKs...
I seem to remember it was added later.
Anyway, if your table has primary Keys, try using:
ClassNamePeer.doDelete(deleteObject.getPrimaryKey());
If not, construct an identifying criteria and use this.
Hmm, another thought, based on your Torque can't find it
and JDBC can, is that your Torque.properties setting might
be pointing to a different location than JDBC. E.g.,
development DB for Torque vs JDBC using production DB?
Good luck.
> -----Original Message-----
> From: Ivan Ivankovic [mailto:ivan.ivankovic@pamet.co.yu]
> Sent: Thursday, November 16, 2006 12:42 PM
> To: torque-user@db.apache.org
> Subject: Cache problem after delete
>
> Hi,
>
>
>
> I worked with Torque only for past 2 weeks, and I found it
> very useful.
>
>
>
> I use Torque 3.0 with Postgres and have following problem:
>
> After deleting some concrete object with usual
> ClassNamePeer.doDelete(objectToDelete), I can still see it in
> database when querying for that objects information with plain JDBC.
>
>
>
> When I use any of Torque query methods, via Criteria or
> retrieveByPK(key), object seems to be erased, but some parts
> of application I am working on use JDBC so I can't rewrite
> all code to use Torque BasePeer.executeQuery(queryString).
> Database data for this object can also be seen from Squirrel
> JDBC browser which of course uses plain JDBC.
>
>
>
> I suppose that Torque has some delayed deletion mechanism and
> I need some way to make him do the actual deletion completely
> from database. Is there some kind of "flush" to achieve this?
>
>
>
> Regards,
>
> Ivanko
>
>
Duke CE Privacy Statement
Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org