new branch ?

[Bogdan Vatkov <bv...@globaltech-bg.com>]

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: <Mi...@bmwna.com>
To: <to...@db.apache.org>
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-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
> 

Re: new branch ?

[Scott Eade <se...@backstagetech.com.au>]

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: <Mi...@bmwna.com>
>To: <to...@db.apache.org>
>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