db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Achille Carette (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-28) Capture and creation of non-table entities - constraints, triggers, stored procedures and others
Date Thu, 16 Mar 2006 10:17:01 GMT
    [ http://issues.apache.org/jira/browse/DDLUTILS-28?page=comments#action_12370667 ] 

Achille Carette commented on DDLUTILS-28:

I would say that being independent of the database does not mean support only a (sub)set of
common features. It means being able to flexibly adapt to various implementations.

This means that (for us at least), the schema definition file(s) should contain only once
what is common to all databases (the database structure), but should also provide a way to
define database-specific elements.

I see four points: 
(1) What is to be defined in the schema dtd (for example, should the dtd define elements for
sequences and stored procedures ?).
(1.1) The xml schema used is Turbine's one. What if DdlUtils needs more or different elements
? (DdlUtils needs informations an ORM does not)
(2) How to permit the inclusion of  database-specific definitions in the schma definition
file(s) ?
(3) How to provide a way to get the xml schema definition file(s) from an existing database,
containing the non standard elements.

> Capture and creation of non-table entities - constraints, triggers, stored procedures
and others
> ------------------------------------------------------------------------------------------------
>          Key: DDLUTILS-28
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-28
>      Project: DdlUtils
>         Type: New Feature
>  Environment: SQL Server, Oracle
>     Reporter: Peter Millington
>     Assignee: Thomas Dudziak

> Database build includes many non-table items - commonly constraints, triggers, stored
procedures and others which may be database dependant (Oracle sequences as an example).
> Even the the common entities are generally not transportable between database types.
 The schema should allow multiple versions of each item to be created, one per database type
which the user requires to support.
> Can the ddl-utils package use user-customisable sql templates to create non-standard
items from (new) generic XML tags?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message