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 (athena.apache.org: local policy)
Message-ID: <4FA7E31F.5010709@apache.org>
Date: Mon, 07 May 2012 16:58:39 +0200
From: Thomas Vandahl <tv@apache.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Apache Torque Developers List <torque-dev@db.apache.org>
Subject: Re: custom sql types in Torque 4
References: 
 <OFDA18067B.AA724309-ONC12579F2.0046EFB6-C12579F2.00479DAF@seitenbau.net>
 <4FA52E5E.8000007@apache.org>
 <OFB39F6100.5B654F40-ONC12579F7.002F5A39-C12579F7.002FC1A7@seitenbau.net>
In-Reply-To: 
 <OFB39F6100.5B654F40-ONC12579F7.002F5A39-C12579F7.002FC1A7@seitenbau.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Am 07.05.2012 10:41, schrieb Thomas Fox:
> The question is what to do if our correct mapping is not the mapping the
> user wants....

Well, then, we could be in trouble when trying to get the data from 
JDBC. The one thing I always liked about Torque is that it makes it 
difficult to shoot yourself in the foot. This proposed method is IMO a 
way to make that shooting easier.

Would it be a solution to simply use a one-to-one mapping everywhere? So 
that TIMESTAMP creates TIMESTAMP and not DATETIME?

Bye, Thomas.

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