# MariaDB Jupyter Kernel Restrictions and Limitations

### Restrictions and Limitations

Here's a list of the current restrictions and limitations of the MariaDB Jupyter kernel. Trying to stretch what we listed here is at your own risk, the results and the behavior of the kernel might be at the mercy of the universe :-)

* One cell should only contain a single SQL statement. It can be multi-line, a one liner, it doesn't matter, but it needs to only be a single statement.
* A notebook cell can only contain one line magic command (line magics start with `%`). Everything else within the same cell below the line magic command will be ignored.
* [Magic commands](/docs/connectors/other/mariadb-jupyter-kernel/using-the-kernel/mariadb-jupyter-kernel-magic-commands.md) and SQL statements cannot be mixed within the same notebook cell.
* The kernel does not officially support the [DELIMITER](/docs/server/clients-and-utilities/mariadb-client/mariadb-command-line-client.md#delimiters) (MariaDB specific) client command. It might work, but it shouldn't be used. Rather use the `%%delimiter` cell magic command (see `%lsmagic` for usage information).
* Each SQL statement within a notebook cell should end with the `;` MariaDB default delimiter, except in cells using the `%%delimiter` cell magic command where it should end with the user-specified delimiter.

{% @marketo/form formId="4316" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mariadb.com/docs/connectors/other/mariadb-jupyter-kernel/using-the-kernel/mariadb-jupyter-kernel-restrictions-and-limitations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.