Hi, Frank:

abbreviations
* OO HSQLDB - HSQLDB embedded with OO
  (vs. stand alone HSQLDB connected by JDBC from OO Base GUI)
* DSE - data source explorer

Thanks for your information.

> If you're perfectly okay with typing mere SQL statements, you might
prefer views (except that currently, you cannot edit them - sigh).

Yes.  SQL is preferable in this case.

By "Currently you cannot edit view ..." do you refer to revising SQL
View through OO GUI?  In OO Base 2.1.0, SQL View revision is easy by
using SQL statements through OO CUI (Tools - SQL).

> The latter (unnamed bind parameter) is understood by far more (all?)
databases than the former (named bind parameter).

OO Base 2.1.0 offers 2 solutions for "stored query": GUI Query and SQL
View.

I do not have any problem with that OO currently chooses the unnamed
bind parameter as the greatest common denominator for GUI Query
implementation.  My question is about the SQL View.  SQL View with named
bind parameters in OO HSQLDB does not work in OO Base 2.1.0.  How can I
make it work?  Did I overlook any setting?

A short comparison of SQL View and GUI Query follows.

SQL View with named bind parameters can be created and stored in OO
HSQLDB through OO Base CUI.  However, neither OO Base GUI nor OO DSE
(e.g. from OO Calc) recognizes named bind parameters in SQL View.  No
user dialog would occur.  SQL developers are stuck, despite that named
bind parameter is supported in HSQLDB 1.8.0.7.

In contrast, named bind parameters in OO Query are fully recognized by
both OO Base GUI and OO DSE.

Regards,
Ray

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to