mariadb

NocoDB used as docker: true
NocoDB version: 0.84.15
Database used in NC_DB URL: mysql
Project was created by clicking : New Project by connecting to external database
Database on which spreadsheet is created : mysql
OS on which NocoDB is running: linux (using the official NocoDB image)
Node.js version if running as node: v12.22.10 (from official image)
Database version : *bo

https://github.com/sequelize/sequelize/blob/8a1429d6044123bba3a3f312b2e0c74b0c829990/lib/model.js#L1271

If I create any model with
charset: 'utf8mb4', collate: 'utf8mb4_general_ci'

sequelize translates it to this for mysql

CREATE TABLE IF NOT EXISTS tablename ... ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8mb4_general_ci;

On stepping through the code, it seems that the issu

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

Issue description

This option will improve performance in many scenarios
https://dev.mysql.com/worklog/task/?id=8134

https://www.facebook.com/weixiang.zhai/posts/678596755543802

Discussed in mindsdb/mindsdb#2214

Hi, I'm sure this is probably some configuration error on my end, but am not sure what to do.

I have my project compiling perfectly on my local machine with the compile-time query checks, but when I deploy it to my server I start getting these errors:

error: error occurred while decoding column 0: mismatched types; Rust type `sqlx_core::types::json::Json<[sqlx_core::postgres::connection

Describe the bug

To Reproduce

Steps to reproduce the behavior:

1. Change the row action link to appear on the right side of the table (from the settings UI)
2. Select a table and go to "Browse". For example this one

![image](https://user-images.githubusercontent.com/7452842/1

These files when added magically but not part of git tracked files causes update failure.

reference: frappe/bench#1225

related: frappe/frappe#16616 (you'll find which function create this file in this PR)

Environment

Liquibase Version: 4.6.1

Liquibase Integration & Version: 4.6.1

Liquibase Extension(s) & Version: 4.6.1

Database Vendor & Version: MySQL8.0.27

Operating System Type & Version: MacOS Monterey 12.0.1

Descript

Filtering using name + schema or regex + schema option currently fails with 'name' or 'regex' property required error.

As workaround remove schema filter.

E.g. failing filter:

{
    "schema": {
        "exclude-tables": [
            {
                "regex": "temp_table_.*",
                "schema": "dbo"
            }
        ]
    }
}

Workaround:

`

I currently need to connect to a Cloudera Impala instance in order to make queries and analyses.
It would be nice to be able to integrate this type of connection in DataStation.
I think it might require some sort of use of the Impala ODBC Connector / Driver.
Thanks!