🐛 Bug: Update Nocodb latest

[rcarvalhopiaget]

Please confirm if bug report does NOT exists already ?

• I confirm there is no existing issue for this

Steps to reproduce ?

I updated nocodb using the docker-compose pull command, then docker-compose down and docker-compose up -d

Desired Behavior

I need the table fields and previously inserted names to be as they were before.

Project Details

version: "2.1"
services:
nocodb:
depends_on:
root_db:
condition: service_healthy
environment:
NC_DB: "mysql2://root_db:3306?u=noco&p=password&d=root_db"
image: "nocodb/nocodb:latest"
ports:
- "8080:8080"
restart: always
volumes:
- "nc_data:/usr/app/data"
root_db:
ports:
- "3306:3306"
environment:

Attachments

Look how my noco looked after I updated

[dstala]

@rcarvalhopiaget what version did you upgrade from? what's mysql version that you are working with?

[emre1e]

im always following this steps. Maybe it will help you.

find NocoDB container ID

docker ps

stop NocoDB container NOT THE DB

docker stop <YOUR_CONTAINER_ID>

delete NocoDB container NOT THE DB

docker rm <YOUR_CONTAINER_ID>

find NocoDB image

docker images

delete NocoDB image NOT THE DB

docker rmi <YOUR_IMAGE_ID>

execute sudo docker-compose up -d

[mustafapc19]

@rcarvalhopiaget Can u provide

• Nocodb meta data (records in nc_bases_v2, nc_columns_v2, nc_views_v2 tables in your NC_DB)
• backend logs after upgrade.

We can connect on discord if its more convenient for you. My discord user id is mustafapc19

[rcarvalhopiaget]

I simply renamed the fields and all the data appeared again. Em qua., 8 de nov. de 2023 às 06:25, Muhammed Mustafa < ***@***.***> escreveu:

…

@rcarvalhopiaget <https://github.com/rcarvalhopiaget> Can u provide - Nocodb meta data (records in nc_bases_v2, nc_columns_v2, nc_views_v2 tables in your NC_DB) - backend logs after upgrade. We can connect on discord if its more convenient for you. My discord user id is mustafapc19 — Reply to this email directly, view it on GitHub <#6911 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAG55XUIHNIZT66QDO7SCZDYDNFZJAVCNFSM6AAAAAA7BVBDD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBRGM4TSNJRHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- <http://www.jpiaget.com.br> *Rodrigo Damasceno de Carvalho* Supervisor de Tecnologia da Informação (11) 4367-8303 / (11) 99124-9874 ***@***.***

[rcarvalhopiaget]

I simply renamed the fields and all the data appeared again. Em ter., 7 de nov. de 2023 às 21:49, Raju Udava ***@***.***> escreveu:

…

@rcarvalhopiaget <https://github.com/rcarvalhopiaget> what version did you upgrade from? what's mysql version that you are working with? — Reply to this email directly, view it on GitHub <#6911 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAG55XUS4ZFGITT42BEW3S3YDLJJDAVCNFSM6AAAAAA7BVBDD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBQHAYDMMRVGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- <http://www.jpiaget.com.br> *Rodrigo Damasceno de Carvalho* Supervisor de Tecnologia da Informação (11) 4367-8303 / (11) 99124-9874 ***@***.***

[rcarvalhopiaget]

I simply renamed the fields and all the data appeared again. Em qua., 8 de nov. de 2023 às 05:42, emre1e ***@***.***> escreveu:

…

im always following this steps. Maybe it will help you. find NocoDB container ID docker ps stop NocoDB container NOT THE DB docker stop <YOUR_CONTAINER_ID> delete NocoDB container NOT THE DB docker rm <YOUR_CONTAINER_ID> find NocoDB image docker images delete NocoDB image NOT THE DB docker rmi <YOUR_IMAGE_ID> execute sudo docker-compose up -d — Reply to this email directly, view it on GitHub <#6911 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAG55XSR655G4T7TOT7AOT3YDNAXRAVCNFSM6AAAAAA7BVBDD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBRGMZTEMZRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- <http://www.jpiaget.com.br> *Rodrigo Damasceno de Carvalho* Supervisor de Tecnologia da Informação (11) 4367-8303 / (11) 99124-9874 ***@***.***

[dstala]

Thanks for updating about status @rcarvalhopiaget
We will keep an eye on this to see if we can emulate something similar locally. If you can reproduce issue again, do let us know. Closing this thread for now.