Zeoslib Portal

Maybe it's more correct to add Connection parameter and use Connection.GetMetadata.GetIdentifierConvertor.Quote for this purpose? The routine is called from 2 places only and is not intended for public usage so the change should be painless.

I don't have pending significant changes to 7.2 too.
As for the docs: honestly I couldn't overcome the process. I even installed TeX editor/compiler but it still too damn messy so I just read comments in the code .

Hello Jan,
if widening a metadata query scheme is OK then I agree that's the most correct option. I'll try to make this update this week.

So - what's the final decision?
As fas as I'm concerned, the problem completely lies in generic (for all drivers) methods. I found no FB-specific methods that could be modified to resolve the issue.

So - what's the decision? 1. Add some code around ConvertInterbase6ToSqlType - OK 2. Add GUID fields list property - OK 3. Add GUID domains list property - ? Requires adding domain column but the resulting RS' scheme is common for all drivers so this addition will touch some piece of generic code. A...

Hello Jan, This is what we propose for Firebird in Zeos 7.2. If I understood you correctly, the problem is, that a caller calls GetColumns with the tablename quoted -> "TableName" instead of TableName. So for Zeos 7.2 the Firebird driver should remove the quotes if they are supplied before...

Hello Jan,
this seems reasonable. ConvertInterbase6ToSqlType is called only 3 times so it's better to extend callers - ConvertInterbase6ToSqlType itself is too low-level to deal with configurations.

Hello Jan, we think that in Zeos 7.2 the Firebird driver should be made to accept quoted identifiers and remove the quotes if necessary The problem is that this stuff has no relations to FB: ZDbcResultSetMetadata.TZAbstractResultSetMetadata.LoadColumn ZDbcResultSetMetadata.TZAbstractResultSetMetadat...

Jan, But in any bigger application it would require the developer to do tedious work when he has to specify the fields again and again and again. This is an invitation for human error - either by forgetting to specify the GUID-Fields at all or by spelling errors. The property could be generated prog...

Hello Jan, no it's not the case. Everything is called correctly but then the field name to find ( '"SomeField"' ) is compared with string value from metadata query which not includes quotes ( 'SomeField' ) and of course comparison fails. In fact I did some tests and I suspect there's no su...

I dislike the pattern patch idea. DB scheme is very likely to be unchangeable (or requiring too much efforts especially considering that UID fields are commonly keys). Moreover, what if someone has a field named, say, user_GUIDe ? The same for domain approach. I'd vote for per-dataset option which i...

As far as I see the root of the issue are quoted field names (I told they're evil!). FB query for table metadata executed in TZInterbase6DatabaseMetadata.UncachedGetColumns returns these names unquoted so comparations with quoted name in TZAbstractResultSetMetadata.ReadColumnByName all fail (you can...

OK, I'll have a look.
---
Reproduced the issue on XE2.

Are you telling that selecting fields with aliases produce the same result? Very hardly but who knows... If you provide minimal reproducible database sample or a whole project it will be easier to locate the issue.

There is related topic in FB subforum. I'd suggest to go there and discuss implementation details