hdb | hdb

I got nowhere trying to correct your code even after spending several hours on it, so I started again from scratch. I think you will find that the code below correctly removes a field from a TTable while retaining the correct contents of the remaining record fields.

The DeleteField routine is a stand-alone procedure, but you should find it straightforward to integrate with your existing code. If you want to add or modify fields, I suggest that you start from Mr Sprenger's code as posted in the link. Personally, if I were you I would abandon your RestructureTable as I don't think it is salvageable, I'm afraid.

My Main form has a TTable named DestTable, a DBGrid and a Datasource connected up as you would expect. I then add the code below.

select[n] syntax works only if table is already loaded in memory. The easiest way to get 1st row of HDB table is:

If I got it right, you need to change the upper date of "BETWEEN" clause.

In this case that clause might look like this

The most performant way to aj, assuming the HDB follows the standard conventions of date-partitioned with `p# attribute on sym, is

I think you need to pass the table trade & dbdir as arguments to your function since you're referencing them inside the function.

Is there any indication of what date is failing with a length error? It could be something wrong with one of the partitions.

Perhaps if you try to load one of the dates into memory and sort it manually IE

It turns out, that adding the library as a second resource-root in Keycloaks's liquibase module is actually working. It does not get loaded because Keycloak removes liquibase.ext from the service loader used to find liquibase extensions.

This can be worked around by using the liquibase.scan.packages system property, though.

For all those trying to make Keycloak working with HANA:

• Overriding the liquibase.scan.packages system property causes the library to be loaded
• Now, a class (LoggingService) from liquibase that is referenced in the liquibase-hanadb library, can not be found because it was introduced in liquibase 3.6 and Keycloak comes with 3.5.5.
• When hacking a more recent version of liquibase (3.6.0) into Keycloak's modules, for some reason a changeset only intended for DB2 is being run, causing errors. I suspect an incompatibility between Keycloak's changelogs and the updated liquibase version.

I gave up at this point.

Fuzziness is interpreted as a Levenshtein Edit Distance — the number of one character changes that need to be made to one string to make it the same as another string.

So "sleeping" will match with "seeing" as their is difference of only one character Fuzziness above 2 edit distance is not supported. So value for fuzziness can be only 1 and 2 so it doesn't make sense to allow percentage.

Check this comment in this issue

In all cases the behaviour of fuzziness can be reduced to two integers (as fuzziness above 2 isn't supported anyway): the threshold at which it becomes 1, and at which it becomes 2. Percentage fuzziness used to be supported but was removed, presumably because it suggested that there was more flexibility when really it was just being turned into two thresholds.

Are you suggesting that it should be customisable at the query level, rather than in configuration? If so, some thought would probably need to be put into the syntax, as there could be confusion between settings that define the fuzziness and those that define the length thresholds for fuzziness, which are both integers.

Try to populate an array before set the state like