To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96883


User fs changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|UNCONFIRMED               |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |WONTFIX
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Thu Dec 18 13:46:40 +0000 
2008 -------
> ODBC allows for a definable delimiter, and in there is no reason that the
> delimiter used in ODBC should be compatible with SQL or anything else for
> that matter.

I beg to disagree. What ODBC is fed with are SQL statements - so yes, the ODBC
driver should care for SQL compatibility.

> My thought would be that Base/SQL could always use a predetermined
> delimiter and only at the point when base "talks" to the ODBC driver is the
> delimiter substituted with whatever delimiter the ODBC driver wants to use.

While this would be possible, probably, it would require major changes to Base's
architecture. Also, I am not even sure it would be a good idea, since in all
places where such an SQL statement is displayed to the user, the statement would
be plain wrong (since using the "standardized" quoting character). Not really
something I'd like to answer: "But Base is using this statement, too - why
doesn't it work with my DB outside of Base?". That's a usability issue, IMO.


The alternative sketched above, to extend Base's parser to recognize the
apostrophe as quoting character, is no valid option after all. The problem is
that statements such as
  SELECT 'A' || 'B' FROM 'table' WHERE 'column' LIKE 'C'
are heavily ambiguous. A, B and C might be column names, or string literals. In
the former case, implicit rules (depending on the concrete database) for their
scope might apply, too. Since OOo's parser is used for a variety of databases,
parsing such statements correctly would be up to impossible in some cases.

So, sorry to say, to me this is a WONTFIX. As a bottom line, using the single
apostrophe as quoting character is not supported by OOo Base, and won't be,
since it would make Base more fragile.

What about asking the driver vendor to use another quoting character instead?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to