Fantastic, @Anastasia Dyubaylo !

Congratulations to everyone who is involved! Thanks to all the DC contributors - now your contributions plus IRIS Vector Search technology + SerenityGPT solution will help to find answers quicker and not only in English - try other languages!

Please feel free to share your feedback here, not only negative ;) We are still learning how to leverage properly this innovation and will be glad to any feedback that will help to convert the technology to a true value!

Hi Robert! Yes, this is clearly the case where there is no answer on DC for the question, and AI compiled the answer from what it had, assuming maybe that JDBC and ODBC are "almost" the same, which is not true. That's why we have "Beta" in the service and a certain disclaimer.  

Perhaps for this question the accurate answer should be "I don't have the answer - ask the community." right?

@Hao Ma , there is such a setting in compiler flags:  - e. But usually it is a very dangerous idea not to store global storage within the persistent class. As the storage is being generated, if not presented in a code on a target machine, it can become completely different from the data associated with the class that already exists, and this can lead to unpredictable data losses and failures. 

So usually, it is not recommended practice to delete the storage information from the class other than you are sure that there is no data in the system or it is deleted in advance.