Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
In-Reply-To: <21ca91ec0606140717h2b78205bn77c4c258379f81@mail.gmail.com>
Subject: Re: Performance issues when using postgresql-8.1-404.jdbc3.jar
To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Message-ID: 
 <OFB6AB1C2B.D08AEAA6-ONC125718D.00508254-C125718D.0051109F@seitenbau.net>
From: Thomas Fischer <fischer@seitenbau.net>
Date: Wed, 14 Jun 2006 16:45:26 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


joe.carter@gmail.com schrieb am 14.06.2006 16:17:44:

> I'd read some intention about moving away from Village and the problems
with
> doing that.
> What I might be able to provide is something that starts the process by
> handling simple
> selects which could revert to village for more complex queries.
> No promises though :-)
> I should be able to suggest/rule out some approaches at the very least
> though.

I have already checked the approach to do that some time ago, and doing
simple selects without village is not a problem indeed. The real problem is
that without village, the behaviour of Torque is likely to change in some
subtle way, and some users will have a hard time to make sure that their
application still work. So one would like to make  the transition in one
step, so people have to resolve the issues with that change only one, not
with every release.

    Thomas


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