The ace-in-line filter sends code directly (more or less) CodeRunner's Jobe sandbox for execution. Jobe runs code in a number of languages, but SQL isn't one of them. The SQL question type in CodeRunner is actually a Python3 question that sends the queries to sqlite3. It might be instructive to click Customise on an SQL question and inspect the template.
To run SQL questions with the Ace-in-line filter you need to do the same sort of thing. But it's not trivial and uploading the database file is a bit tricky.
Firstly, to upload an sqlite3 database file for the code to operate on, you need to use one of the two file-upload methods supported by ace-in-line. However, neither method supports binary files, and sqlite3 databases are binary. So you have to first encode the database in a text format such as base64 and insert it into a hidden textarea (assuming use of the data-file-taids method).
Next, you need to insert a <script> element that defines a JavaScript function for use as a code-mapper, to wrap the SQL code from the Try it! box into a Python3 program that decode the database file back to binary and then run the sql code using sqlite3.
Lastly you need to configure a <pre> element that uses the data-ace-lang attribute to set the Ace language to sql, the data-file-taids attribute to get the file from the (hidden) textarea and the data-code-mapper to reference the wrapper function you wrote in the <script> element.
If, after reading all that, you're still interested, I've added a demo of an SQL Try it! box to the
Ace-in-line filter demo on this site. Scroll down to the section
SQL: another example of using a code-mapper. Play with it a bit to see if it does what you want. If so, view the source of page to see what's going on under the hood. You should be able to mostly just copy-and-paste the raw HTML out of that page for your own use.