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: neutral (nike.apache.org: local policy)
Message-ID: <5152A4AA.8010503@apache.org>
Date: Wed, 27 Mar 2013 08:50:02 +0100
From: Thomas Vandahl <tv@apache.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Apache Torque Developers List <torque-dev@db.apache.org>
Subject: Re: torque 4.1 plans
References: 
 <OFBE4A0C90.0C9AA833-ONC1257B34.0002ACCD-C1257B34.00056CF8@seitenbau.net>
In-Reply-To: 
 <OFBE4A0C90.0C9AA833-ONC1257B34.0002ACCD-C1257B34.00056CF8@seitenbau.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Thomas,

On 20.03.2013 01:59, Thomas Fox wrote:
> Personally, I'd like to remove the deprecated APIs, especially the old
> Criteria implementation, from the runtime.
+1

> So these are the things I'd like to tackle.
> Does anyone else have any other plans ?
I'd like to suggest two additional playgrounds:
- Further reduction of static classes in the runtime
- Handling of CLOBs/BLOBs. Currently, the data is loaded into memory 
(byte array or String) This can be dangerous when the L in BLOB really 
means *Large*. JDBC provides a possibility to read/write this data as a 
stream. I'd like to expose this functionality to the Torque API somehow. 
(Not entirely sure if that is possible at all)

> Are there objections against
> - adding groovy as additional template language to the generator
> - adding typed models to the generator
> - try to use convention over configuration in the generator
> - starting an eclipse plugin elswhere

All +1. The eclipse plugin could as well be hosted in the Torque SVN, IMO.

Bye, Thomas.


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