Is it normal to get truncated identifiers after applying SQL schema of RegaDB?
0
0
Entering edit mode
12 months ago

Hello, everyone

I am trying to set up RegaDB on my CentOS system, and I have installed PostgreSQL via conda. I followed the RegaDB installation manual to configure the PostgreSQL database. However, when I have applied the postgresSchema.sql schema from the RegaDB software package, I noticed several NOTICE messages about truncated identifiers.

Here is a sample of the output I received:

psql:postgresSchema.sql:25: NOTICE:  identifier "query_definition_parameter_type_query_definition_parameter_type_ii_seq" will be truncated to "query_definition_parameter_type_query_definition_parameter_type"
psql:postgresSchema.sql:27: NOTICE:  identifier "query_definition_run_parameter_query_definition_run_parameter_ii_seq" will be truncated to "query_definition_run_parameter_query_definition_run_parameter_i"
psql:postgresSchema.sql:29: NOTICE:  identifier "resistance_interpretation_template_resistance_interpretation_template_ii_seq" will be truncated to "resistance_interpretation_template_resistance_interpretation_te"

I understand that PostgreSQL has a maximum identifier length of 63 bytes, and identifiers exceeding this limit will be truncated. My question is whether these truncated identifiers will cause any issues with the proper functioning of RegaDB. If so, what would be the best approach to fix this issue?

I would appreciate any guidance on this matter, and if there are any additional precautions or testing measures I should take to ensure RegaDB functions as expected.

Best regards,
Pavel

regadb postgresql hiv • 386 views
ADD COMMENT

Login before adding your answer.

Traffic: 1883 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6