Question is, are we able to use this like a regular DQL ?

ExecDQL is the best thing since white bread.

ExecDQL is just DQL but the point of it is that it isn’t regular DQL.

ExecDQL is DQL as a function so it doesn’t create any output directly other than an export file if you want to. That option is not fully developed either, as for now it will only export ~ separated in field order with no headers.

The ExecDQL export however is blitzingly fast. (which you can’t say for anything in regular DQL)

And you can manipulate the file after by adding a header with WriteToFile() or MemoWriteToFile().

I don’t use “Regular” DQL anymore. That implementation of DQL has always annoyed me to bits. It is sloppy, buggy, difficult, annoying and slow and it is a mystery how it has survived for 20 years….

ExecDQL was designed to allow users to use DQL more extensively as an integral part of their application (i.e. without all the window resizing etc. that regular DQL cause), and as it turns out you can use DQL even more than you think.

We didn’t know before we made it that we would inherit the Object context of the document calling it, so now you can use it to manipulate objects in the form directly from a DQL, and as  you can tell we use it quite extensively  in the samples.

But before I go on… What do you mean with “are we able to use this like a regular DQL ?”

What is it you want to use it for?