db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Leng <wl...@metatomix.com>
Subject Re: Village Fork
Date Mon, 15 Aug 2005 14:16:21 GMT
I guess getting rid of village will not solve the lob problem. The lob 
problem is deeply rooted in the JDBC drivers. Torque cannot support lob 
stuff without doing some like
if(oracle) doThis
else if(db2) doThat
else ....

Bill

Thomas Fischer wrote:
> Henning,
> 
> it is really nice of you to offer that. My own _PERSONAL_ feelings about 
> it are as follows:
> The biggest problem which I have with village is the oracle lob stuff. I 
> am using Saravanna Kannan's version of villag with oracle, which works 
> fine if one just uses oracle, but does not work with other databases. My 
> feeling is that creating a version which supports both oracle lobs and 
> other databases is too much work considering that we want to chuck out 
> village anyway.
> 
> So thanks for the offer, but for me as a Torque user it does not help me.
> 
>   Thomas
> 
> 
> On Sun, 7 Aug 2005, Henning P. Schmiedehausen wrote:
> 
>> Thomas Fischer <tfischer@apache.org> writes:
>>
>>> On Thu, 4 Aug 2005, Robert Dietrick wrote:
>>
>>
>>>> The only remaining question now is: why on earth does Torque query the
>>>> database meta data before inserting when the OR mapping provides all 
>>>> the
>>>> information the system needs about the database?
>>>>
>>
>>> This is one of the problems associated with the usage of the village
>>> library. Not being one of the orignial authors of Torque, it seems that
>>> using this library has sped up the development of Torque quite a lot in
>>> the beginning, but now it is limitating Torque in quite a few places. It
>>> might happen that at some point, the village library is thrown out of
>>> Torque, but village is linked deeply into Torque, so this will be a 
>>> lot of
>>> work and is also likely to cause some trouble.
>>
>>
>> Just a quick opinion poll between our users:
>>
>> As Village is a constant source of pain and those that are currently
>> using the 3.1 branch of Torque and probably also the 3.2 release will
>> be stuck on Village:
>>
>> Any interest from you if I just whip up a small "branched Village"
>> site outside of the ASF, apply all the patches to the village tree
>> that you like to see and then just build a "village-<some
>> version>.jar" that we can distribute through ibiblio?
>>
>> This wouldn't be a hard thing to do and though the plans for post-3.2
>> releases are to get rid of village, this might help our current users
>> in the short run.
>>
>> As I already have a village tree that builds with maven, building a
>> site would be no big deal.
>>
>>     Regards
>>         Henning
>>
>>
>> -- 
>> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
>> hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/
>>
>> RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for 
>> hire
>>   Linux, Java, perl, Solaris -- Consulting, Training, Development
>>
>>               4 - 8 - 15 - 16 - 23 - 42
>>
>> ---------------------------------------------------------------------
>> 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
> 

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


Mime
View raw message