Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: torque-dev@db.apache.org
To: torque-dev@db.apache.org
Subject: =?iso-8859-1?q?=5BDB_Torque_Wiki=5D_Updated=3A__GettingTorqueToWork?=
Date: Tue, 27 Apr 2004 15:55:25 -0000
Message-ID: <20040427155525.64431.6124@minotaur.apache.org>

   Date: 2004-04-27T08:55:25
   Editor: 206.98.174.49 <>
   Wiki: DB Torque Wiki
   Page: GettingTorqueToWork
   URL: http://wiki.apache.org/db-torque/GettingTorqueToWork

   no comment

Change Log:

---------------------------------------------------------------------------=
---
@@ -113,6 +113,12 @@
 =

 -- DanielSavard (2004-03-29)
 =

+This is somewhat related to the problem encountered by Pete. Received a 'g=
enerator.parse' error using the default target from Ant.
+
+The problem turned out to be from a datatype in the source Oracle schema. =
Used the torque 'jdbc' task and the resulting xxx-schema.xml file had an em=
pty type attribute for any columns which were defined as Timestamps in the =
source Oracle schema. Modified the original ddl to change all Oracle 'Times=
tamp' columns over to the type 'Date'. Once I rebuilt the schema in Oracle,=
 re-ran the torque jdbc task, torque's default (main) task worked fine.
+
+-- Kyong Park (2004-04-27)  =

+
 =3D another hint =3D
 =

 If you get an error like:

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