Quoted identifiers in SQL Database (Firebird)

rbuser

I have created an application with uses IBO 4.2 with Firebird 1.5.
During the creation of tables I used quotes(") on all fields which is
permitted under SQL92.
The RB Data Dictionary complains about the quotes.
All other aspects of my development has not been affected only enhanced by
the use of quoted names.
Is there a solution or likely to be a solution to this problem.
Thanks

Trevor Watters

digitalmetaphors

We are not explicitly supporting quotes in the table names and field names
definitions. We are not going to attempt to support this spec in SQL92.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Hi Jim,

There was no warning on your product features or limitations regarding non
support of an increasingly requested part of SQL specification.

As I have indicated, ALL the other sql tools and components I use during
development have no problems with quoted and parts of RB Pro have no
problems.

Is your "not going to attempt" a final word on this subject??

Trevor

digitalmetaphors

We can research this further to see if DADE could easily support it, but
initial indications lead us to believe that this feature would ripple
through the DADE library and it would not be a quick fix to implement. I'll
add it to the ToDo list and we will evaluate the feasibility of adding this
feature when we move through the ToDo list.


Cheers,

Jim Bennett
Digital Metaphors

rbuser

Thanks for that.
AFI can tell, generating the Table List works if you remove the test for
quotes in ppUtils.pas but then generate Fields List fails because it
enquotes an already enquoted table name.
If I use and existing query, the Report Designer works with quoted fields
and produces a report.
Given your response and a its unknown timeframe, I'll have to redevelop my
Database and changed all my SQL queries to avoid the use of quotes. Please
warn other developer about this.
Of course, my other alternative is to learn and correct your source and hope
that all dcu's without source don't have any impact on the solution.

Kind regards

Trevor Watters

digitalmetaphors

You could implemente this change in our source and still use RAP, but only
on one condition. If you don't change the interface section of any of our
source units, then you can still link in the RAP dcu's with a modified
version of our source. You can change the implementation section of our
classes to implement the modifications if you want to attack this problem in
our rather than change you database structure.


Cheers,

Jim Bennett
Digital Metaphors