From torque-dev-return-4222-apmail-db-torque-dev-archive=db.apache.org@db.apache.org Fri Jun 18 13:01:29 2004 Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 45423 invoked from network); 18 Jun 2004 13:01:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 18 Jun 2004 13:01:29 -0000 Received: (qmail 15065 invoked by uid 500); 18 Jun 2004 12:57:47 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 14656 invoked by uid 500); 18 Jun 2004 12:57:43 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 14397 invoked by uid 99); 18 Jun 2004 12:57:41 -0000 Received: from [202.4.235.137] (HELO barge.anchor.net.au) (202.4.235.137) by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 18 Jun 2004 05:57:40 -0700 Received: from [192.168.0.2] (CPE-138-130-149-222.nsw.bigpond.net.au [138.130.149.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by barge.anchor.net.au (Postfix) with ESMTP id 476631009D for ; Fri, 18 Jun 2004 22:57:32 +1000 (EST) Message-ID: <40D2E6B7.8000801@backstagetech.com.au> Date: Fri, 18 Jun 2004 22:57:27 +1000 From: Scott Eade User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache Torque Developers List Subject: Re: new branch ? References: <007201c443b8$111ca570$690ba8c0@int.globaltechbg.com> In-Reply-To: <007201c443b8$111ca570$690ba8c0@int.globaltechbg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Sorry for the delayed reply Bogdan, been busy IRL. I am reluctant to go with a branch for this work. The trouble is that unless you can find time to document your work there is little point having it in CVS. Torque is clearly in need of new committers and I think it would be really great if you and others stepped forward to take on these roles and help Torque to move forwards. I suggest you limit your fixes to specific self-contained changes that include and necessary documentation updates and where possible test cases. Post patches to this list and by all means if nothing is happening then feel free to send me the occasional reminder off-list. After a few of your patches have been accepted and committed the process of becomming a committer is fairly straightforward. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au Bogdan Vatkov wrote: >Hi, I have made a lot of fixes to the code to support fully qualified names >and I am thinking of comitting to the CVS ina different branch ..but i still have no time to >make corresponding docs to the changes have made ... >anyway I use successfully fully qualified names with postgres > >To Developers: >Is it possible for me to create a branch ? to upload the fully qualified names and >the SERIAL type ( sql proper generation and reverse (jdbc goal)) in postgres. >I have a lot of fixes in the code and I have developed new packages to support >data representation/manipulation code (stuff like representing of nested objects, authorizing across all the data model mechanisms etc.) > >What do you think , should I be able to commit to the CVS ? > >Thanx, >Bogdan > >----- Original Message ----- >From: >To: >Sent: Thursday, May 27, 2004 2:03 AM >Subject: Torque TODO List Regarding Fully Qualified Table Names > > > > >>Hi- >> >>I've checked the web site but I'm wondering if it's on the to-do list to add >>fully qualified table functionality to Torque in the near future. >> >>It seems as though many users have opted out of using Torque primarily due >>to this reason. I too have been checking over the last year hoping that >>this feature would be integrated. >> >>Any thoughts? >> >>Michael >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org