Hi, OO Base community: alternative keys * SQL named parameter * SQL named bind parameter * SQL unnamed bind parameter
* SQL named parameter in multi-tier SQL statements (queries/views stored on DB engine side) HSQLDB 1.8.0.7 already supports SQL named parameter. This support is inherent in HSQLDB and independent of OO Base GUI. Apparently OO Base 2.1.0 also supports access to SQL named parameter implemented in whatever database engines, based on the following info.: * documentation.openoffice.org/HOW_TO/data_source/link_tablehtml/link.html #6.Enabling Use of Named Parameters for the Data Source|outline * www.openoffice.org/issues/show_bug.cgi?id=2794 I could not figure out how to turn on the named parameter for HSQLDB data sources in OO Base through OO Base GUI, without using the OO Basic script, as suggested in OO Issue 2794. The resolution "fixed" in OO Issue 2794 implies that OO Base already has the UI code to collaborate with database engine (no UI) for the named parameters in queries/views stored on the engine side. In addition, is there a way to set the default through OO Base GUI for the named parameter option for "all" data sources in OO Base? Please note an implementation subtlety in OO Base stored query. OO Base 2.1.0 GUI currently contains query capability that partially duplicates the SQL queries and SQL views stored on the database engine side. Let us call them the GUI query and SQL query for the sake of brevity. Although their usage seems initially similar to casual users, they are very different for database development and deployment purposes. GUI query is stored on the OO GUI specific side (XML part of zip), and SQL query in the HSQLDB specific side (database\* of zip), or SQL query in a separate file for an external HSQLDB (not embedded in OO Base), or SQL views in yet another file for linked tables (virtual tables, etc.). The naturally conform to syntax rules as mandated by DB engines (HSQLDB, MySQL, Oracle, etc.) and GUI that might differ and that will continue to evolve in competition. The revision and update strategy will be different for a server and client configuration in business environment. There is also potential impact on the execution of multi-tier SQL statements as well as handling hierarchical data in RDBMS. Thanks for advice. Ray --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
