Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dtp-dev] Firebird enablement in DTP


I am assuming that you are using the default DDL generator. You can implement the DDLgeneration extension point defined in connectivity.sqm.core plugin. So that in your implementation you can then ignore the schema in the DDL generation. org.eclipse.datatools.connectivity.derby plugin has the example code implementing the extension point for DDL generation.


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

Roman Rokytskyy <rrokytskyy@xxxxxxxxxxx>
Sent by: dtp-dev-bounces@xxxxxxxxxxx

02/26/2007 11:23 PM

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

DTP development mailing list <dtp-dev@xxxxxxxxxxx>
Re: [dtp-dev] Firebird enablement in DTP


> I think the practice for schema-less databases (notably MySQL) is to
> dummy-out the schema with the database name.  Thus, at least for MySQL,
> the qualified name would be correct and the schema object would never be
> null.  Obviously, we can revisit this issue when we fix the defects but
> I thought the information might help you workaround your current issues.

Yes, this would work for DSE view (that's what I did), but it won't help
when the SQL is generated - Firebird's parser does not accept the
<something>.<tablename> notation. This was already briefly discussed
among the Firebird developers, but the proper schema support won't be
there at least for the next 2 years.

dtp-dev mailing list

Back to the top