>>Ok, this makes a bit more sense then. Yes, i do not ask exacly about BIND only all SET commands
>> Although why obtain it through MON$STATEMENTS, when that is what the >> information API is for. >>And keep in mind that querying MON$STATEMENTS is relatively expensive, so >>building a feature that requires use of MON$STATEMENTS might not always be a >>good idea. Explained plan (legacy form) is already in MON$STATEMENTS as preview of all running queries. And when more formats will be available like XML, JSON, then it is convenient to have way to change it also there. >>The SQL standard defines a number of session management statements that all start with SET: >>So in that way, using SET for bind configuration, etc, seems a logical >>extension. Now it is understandable why SET is prefered. And `SET LOCAL` extensions will be good for some commands. Thank you for the info. regards, Karol Bieniaszewski Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
