Return-Path: Mailing-List: contact turbine-torque-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list turbine-torque-dev@jakarta.apache.org Received: (qmail 14924 invoked by uid 98); 6 Jan 2003 04:15:24 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 14905 invoked from network); 6 Jan 2003 04:15:22 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 6 Jan 2003 04:15:22 -0000 Received: (qmail 18623 invoked by uid 500); 6 Jan 2003 04:13:56 -0000 Received: (qmail 18616 invoked from network); 6 Jan 2003 04:13:56 -0000 Received: from smtp.comcast.net (24.153.64.2) by daedalus.apache.org with SMTP; 6 Jan 2003 04:13:56 -0000 Received: from THAILAND.pobox.com (pcp01334892pcs.fairmt01.pa.comcast.net [68.81.128.25]) by mtaout02.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.07 (built Nov 25 2002)) with ESMTP id <0H8900JF6YFAZJ@mtaout02.icomcast.net> for turbine-torque-dev@jakarta.apache.org; Sun, 05 Jan 2003 23:13:59 -0500 (EST) Date: Sun, 05 Jan 2003 23:15:00 -0500 From: tek1 Subject: Re: [PATCH] locating database.dtd / PATCH for postgresql table/column names In-reply-to: X-Sender: (Unverified) To: Turbine Torque Developers List Message-id: <4.3.2-J.20030105231116.03309568@smtp.comcast.net> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2-J Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <4.3.2-J.20021223200826.0330d710@smtp.comcast.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ok, will do, but what is the cvs login info? it's not mentioned anywhere on the torque page. i have a few other patches related to postgresql .sql generation, specifically the table name and column names needing double quotes around them. otherwise, when you execute the sql without the double quotes, postgresql automatically makes the entire table name or column lowercase. for example, "loginId" defined in the table creation sql becomes "loginid" in the database. i've fixed this locally, but need to know the cvs info to get you the diffs. thanks. At 08:29 02/12/31 +1100, you wrote: >"tek1", > >Patches are welcome, but can you please do the following: > >1. Create unidiff patch files (cvs diff -u) >2. Create a patch issue in the appropriate module in Scarab >(http://scarab.werken.com/scarab/issues/) that describes the problem and >attach your patch file. In this case the module would be "Torque > Source". > >Thanks, > >Scott >-- >Scott Eade