<p><em>This question was also asked on <a href="https://www.biostars.org/p/9562091/" rel="nofollow noreferrer">Biostars</a></em></p>
<p>I am trying to set up <a href="https://rega.kuleuven.be/cev/regadb" rel="nofollow noreferrer"><strong>RegaDB</strong></a> on my <strong>CentOS</strong> system, and I have installed <strong>PostgreSQL</strong> via <code>conda</code>. I followed the <strong>RegaDB</strong> installation manual to configure the <strong>PostgreSQL</strong> database. However, when I have applied the <em>postgresSchema.sql</em> schema from the <strong>RegaDB</strong> software package, I noticed several <code>NOTICE</code> messages about truncated identifiers.</p>
<p>Here is a sample of the output I received:</p>
<pre><code>psql:postgresSchema.sql:25: NOTICE:  identifier &quot;query_definition_parameter_type_query_definition_parameter_type_ii_seq&quot; will be truncated to &quot;query_definition_parameter_type_query_definition_parameter_type&quot;
psql:postgresSchema.sql:27: NOTICE:  identifier &quot;query_definition_run_parameter_query_definition_run_parameter_ii_seq&quot; will be truncated to &quot;query_definition_run_parameter_query_definition_run_parameter_i&quot;
psql:postgresSchema.sql:29: NOTICE:  identifier &quot;resistance_interpretation_template_resistance_interpretation_template_ii_seq&quot; will be truncated to &quot;resistance_interpretation_template_resistance_interpretation_te&quot;
</code></pre>
<p>I understand that <strong>PostgreSQL</strong> has a maximum identifier length of <em>63</em> 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 <strong>RegaDB</strong>. If so, what would be the best approach to fix this issue?</p>
<p>I would appreciate any guidance on this matter, and if there are any additional precautions or testing measures I should take to ensure <strong>RegaDB</strong> functions as expected.</p>
<p>Best regards,</p>

CC BY-SA 4.0
2023-04-30T20:22:52.503Z
Hi @Vovin I would make sure RegaDB is not abandonware. Its [github](https://github.com/plibin/regadb) hasn't been updated for 9 years. PostgreSQL will have been revised many times since then and will not be the version used to develop RegaDB. Upvoted anyway.
M__
CC BY-SA 4.0
2023-05-02T21:50:44.203Z
@M__ I suppose that newer versions of **PostgreSQL** (as well as **Tomcat**) actually caused a bunch of my fail attempts to run **RegaDB**. But the maximum length of identifiers is a substantially base thing in **PostgreSQL**, as it is set by the constant `NAMEDATALEN` at the compilation step.
Vovin
<hiv>
Is it normal to get truncated identifiers after applying SQL scema of RegaDB?
# Is it normal to get truncated identifiers after applying SQL scema of RegaDB?

(Asked by: username_0 on 2023-04-30)

This question was also asked on Biostars
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,

**Tags:** hiv
> **Comments:**
> **username_1**: Hi @Vovin I would make sure RegaDB is not abandonware. Its [github](https://github.com/plibin/regadb) hasn't been updated for 9 years. PostgreSQL will have been revised many times since then and will not be the version used to develop RegaDB. Upvoted anyway.  
> **username_0**: @M__ I suppose that newer versions of **PostgreSQL** (as well as **Tomcat**) actually caused a bunch of my fail attempts to run **RegaDB**. But the maximum length of identifiers is a substantially base thing in **PostgreSQL**, as it is set by the constant `NAMEDATALEN` at the compilation step.  

---

## 0 answers

