Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Date: Fri, 26 Aug 2005 13:38:50 -0700 (PDT)
From: Thomas Fischer <tfischer@apache.org>
To: torque-user@db.apache.org
cc: james_long@provima.com
Subject: Re: getDate()
Message-ID: <20050826133044.C7984@minotaur.apache.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Hi,

I have created an issue on that, just that it is not forgotten.
See

http://issues.apache.org/scarab/issues/id/TRQS319

However, I am afraid that it probably will not make into 3.2 on itself.

    Thomas

Trey Long <james_long@provima.com> wrote

> I agree with that conclusion, with certain functions such as getDate()
> it wouldn't be valid until insert. At that point the object could pull
> back the correct information.
> 
> In that case the only real solution is to allow torque to gracefully
> handle default formula's and let the database do it's job. As far as
> using the object before-hand though I don't know how that would be
> handled, perhaps some method to indicate whether... I have no idea. At
> this point, this it totally in your realm :)
>
> 
> Thomas Fischer wrote:
> 
>>
>>
>> I do not see any possibility that the object could handle a database
>> function on construction. The object would have to ask the database to
>> execute the function, and this process is different on different 
>> databases.
>> On Oracle, for example, one would have to do something like (Select
>> getDate() from dual), and this would certainly not work on any other
>> database.
>> 
>> The only possibility I see at the moment is to refresh the object from 
>> the
>> db and then get the inserted value.
>> 
>>     Thomas

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