Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dtp-dev] sql model validation


Der Ping,
        The default validator and the extension point are exactly what I'm thinking. I assume this component should be contained in model base project, right?

Best Regards!

Max ( Hui ) Cao
Sybase, Inc. Shanghai, China



Der Ping Chou <dpchou@xxxxxxxxxx>
Sent by: dtp-dev-bounces@xxxxxxxxxxx

11/11/2006 05:28 AM

Please respond to
DTP development mailing list <dtp-dev@xxxxxxxxxxx>

To
DTP development mailing list <dtp-dev@xxxxxxxxxxx>
cc
DTP development mailing list <dtp-dev@xxxxxxxxxxx>, dtp-dev-bounces@xxxxxxxxxxx
Subject
Re: [dtp-dev] sql model validation






Rob,


In line with your comment. The model validation should cover the basic, which is based on the relationship between model elements, such as containment, dependency....etc. For instance, table contains no column or table contains no PK or a FK's referenced/depending on a PK/Index does not exist. The default validator should support what is given and further provides extension point to allow consumer to implement extention point to provide domain specific validation.


The extension point mentioned above would be very much inline with what you are proposing.


My two cents.


Der-Ping Chou
Information Management Tooling
Development Manager - Data Tools
Seattle IBM Office
tel : 1-206-587-5946 (T/L: 277-5946)
fax: 1-206-587-4415



rcernich@xxxxxxxxxx
Sent by: dtp-dev-bounces@xxxxxxxxxxx

11/10/2006 07:39 AM

Please respond to
DTP development mailing list <dtp-dev@xxxxxxxxxxx>

To
DTP development mailing list <dtp-dev@xxxxxxxxxxx>
cc
Subject
Re: [dtp-dev] sql model validation







Hey Hui,

>         Do we have any plan to support sql model validation? e.g. a
> table should at least contain one column and column names can not
> duplicate. The default validator should support extension so that
> vendors can customize the validation algorithm.
>


Could you provide a use case?  Are there cases where the model is not
populated via a catalog loader where validation would be required? My
assumption is that the catalog loader always populates a valid model (i.e.
for your example, my assumption would be that the DB  wouldn't let you
create a table with no columns and therefore a table with no columns would
never show up in a model instance, unless there was an error during
loading, in which case we should be notifying the user of the error in some
way).

Thanks in advance,
Rob

_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev

_______________________________________________
dtp-dev mailing list
dtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-dev


Back to the top