[BUG] Error while creating a list

[hubdesk]

From: Andrea Romero andrearomerov@gmail.com

Am trying to create a list, it says the list (perpetradores) already exists
but it is nowhere to be found. I change the name, I progress beyond the
name and then I get the error screen

A

--

Attachments

• [SQLSTATE[42000]Syntax error or access violation 1103 Incorrect table name 'perp' (SQL create table list_perpetrador_c_o_s (id char(36) not null, created_at timestamp null, updated_at timestamp null, deleted_at timestamp null, perp._c_.pdf](https://hubdesk.io/dashboard/b9a709ec-2a28-440a-8984-c029f3d6bc60/inboxes/253d6580-14b1-41a0-a587-fae4bb82eb56/threads/d0738bda-acd8-4595-9c23-7bd2cca5aa4a/messages/dd8e0e2d-cc38-4035-b2c2-d32fccf99753/attachments/SQLSTATE[42000]__Syntax error or access violation_ 1103 Incorrect table name 'perp' (SQL_ create table list_perpetrador_c_o_s (idchar(36) not null,created_attimestamp null,updated_attimestamp null,deleted_attimestamp null,perp.c.pdf)

[github-actions]

AI-Assisted Response:

Issue Summary

List Creation Failure and Subsequent Error Message

Andrea Romero is encountering an issue while attempting to create a list named "perpetradores." The system erroneously reports that the list already exists, even though it cannot be located by the user. After renaming the list to circumvent this problem, an error occurs. The error message indicates a syntax error or access violation related to an incorrect table name 'perp' during an SQL operation to create the table list_perpetrador_c_o_s.

Issue Category

• Bug

Clarification Questions

• @HubDesk[bot], could you provide the exact steps you are taking to create the list which results in the error message?
• Can you confirm if the issue arises when using a particular tool or interface within the application?
• Is there more information in the error log that could clarify at which point during the list creation process the error is triggered?
• Have you encountered this issue with other list names or just specifically with "perpetradores"?
• Could you specify the version of the software or platform you are using when this error occurs?
• Is there any stack trace or additional context around the SQL error message that might help to diagnose the issue further?

[lduf]

Duplicate issue : #432