Problem with new MYSQL Nodes

[Tim_C]

Describe the problem/error/question

Getting an error when using the new mysql ndoes as update / insert or upsert
The old nodes work fine

What is the error message (if any)?

ERROR: Cannot read properties of undefined (reading ‘split’)

Note: None of the fields are called split

Please share your workflow

Share the output returned by the last node

{
“id”: 3755376883,
“summary”: “-snip-”,
“description”: “-snip- this contains HTML if that matters.”,
“customer_id”: null,
“created_at”: “2023-05-24T16:08:19.363+10:00”,
“updated_at”: “2023-05-24T16:08:22.432+10:00”,
“start_at”: “2023-05-25T12:00:00.000+10:00”,
“end_at”: “2023-05-25T13:00:00.000+10:00”,
“duration”: 1,
“location”: “-snip-”,
“ticket_id”: 67125589,
“location_type”: null,
“start_at_label”: “25 May, 2023 12:00”,
“all_day”: false
}

Information on your n8n setup

• n8n version: 0.230.3
• Database (default: SQLite): MariaDB
• n8n EXECUTIONS_PROCESS setting (default: own, main): queue
• Running n8n via (Docker, npm, n8n cloud, desktop app): docker
• Operating system: ubuntu 22.04

[MutedJam]

Hi @Tim_C, I am sorry you’re having trouble.

Based on the information you have provided, I have started a MariaDB setup using the below docker compose file:

services:
  
  n8n:
    image: n8nio/n8n:0.230.3
    restart: unless-stopped
    ports:
      - 5678:5678
    volumes:
      - ./n8n_data:/home/node/.n8n
  
  mariadb:
    image: mariadb:latest
    restart: unless-stopped
    ports:
      - 3306:3306
    environment:
      - MARIADB_ROOT_PASSWORD=123456
    volumes:
      - ./mariadb_data:/var/lib/mysql

I have then created a table schema based on the information you have provided and guesses about the exact data types your table is using:

CREATE TABLE appointments (
    id BIGINT PRIMARY KEY,
    summary VARCHAR(255),
    description TEXT,
    customer_id INTEGER,
    created_at TIMESTAMP,
    updated_at TIMESTAMP,
    start_at TIMESTAMP,
    end_at TIMESTAMP,
    duration INTEGER,
    location VARCHAR(255),
    ticket_id BIGINT,
    location_type VARCHAR(255),
    start_at_label VARCHAR(255),
    all_day BOOLEAN
);

INSERT INTO appointments (id) VALUES (3755376883);

I then executed the below workflow, creating your example dataset using the Code node and then running the MySQL node you have provided:

I could not reproduce your specific problem but would instead see an “Incorrect datetime value” message coming from MariaDB:

That’s obviously not the error you have seen (and will be a problem with my database/table schema), so I am afraid I am not quite sure what’s wrong in your case.

Can you provide more detailed steps on how someone with no access to your specific database can reproduce the problem? And are you perhaps able to perform your update by providing an UPDATE query through the Execute SQL operation of the MySQL node?

[Tim_C]

Hi Sorry, I should have been more clear.

My n8n backend is mariadb, but my mysql that im interacting with is “mysql:8.0.33”

Heres a snippet of the docker file for it:

db:
image: mysql:8.0.33
command:
- mysqld
- --innodb_buffer_pool_size=512M
- --character-set-server=utf8mb4
- --collation-server=utf8mb4_unicode_ci
- --skip-log-bin
- --max_connections=100
- --max_allowed_packet=128M

Not sure if that matters?

[MutedJam]

Hi @Tim_C, even with MySQL instead of MariaDB the test workflow still completes for me:

The data still looks accurate to me:

So I’d need more details on how exactly I could reproduce your problem I’m afraid.

[Tim_C]

Hmm, thanks for trying. It worked fine on a different workflow, so it must be in the source data. I’ll keep testing and come back if I find out exactly what triggered it.