Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Subject: schema.xml
From: Hilco Wijbenga <hilco.wijbenga@elasticpath.com>
Reply-To: hilco.wijbenga@elasticpath.com
To: Apache Torque Users List <torque-user@db.apache.org>
Content-Type: text/plain
Organization: Elastic Path Software, Inc.
Date: Wed, 09 Nov 2005 16:50:36 -0800
Message-Id: <1131583836.6341.57.camel@hwijbenga.dev.elasticpath.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

The database name is currently stored in the schema.xml file. This
requires that I define the database name in two places: in my
build.properties and in schema.xml. Notably, the developers change the
database name in build.properties and, of course, the build will fail:
the name in build.properties is not leading.

The database name is not really part of the schema. I can create the
same schema several times with different names.

I would like to propose that the 'name' attribute in schema.xml be
optional instead of required. If it's there it will be used (preserving
backward compatibility) otherwise the Ant task needs to supply the name.
(Or maybe, supplying a name throught the Ant task could overrule the
name in schema.xml?) Not supplying a name at all would be an error.

Thoughts?

Thanks,
Hilco


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