Same database view in different environments generates different cdt

RE: Same database view in different environments generates different cdt

Mathieu Drouin — Fri, 28 Feb 2025 21:16:24 GMT

You have to do it on the underlying table (the one that the view uses).

Speaking of which, I see that you posted the structure for the view, but could you check the structure of the underlying table?

RE: Same database view in different environments generates different cdt

Chiara Gambone — Fri, 28 Feb 2025 17:32:13 GMT

Putting the XSD to mediumtext moves the issue from one environment to the other, when I change it it stops verifying in Test and works in Dev.

As to setting the column to longtext, how do i do it for a database view? I had searched on the web but hadn't find a way to define the type

RE: Same database view in different environments generates different cdt

Mathieu Drouin — Fri, 28 Feb 2025 17:25:17 GMT

Why not just update the database column to longtext or the XSD to use mediumtext?

RE: Same database view in different environments generates different cdt

Mike Schmitt — Fri, 28 Feb 2025 17:08:40 GMT

[quote userid="66765" url="~/discussions/f/data/38574/same-database-view-in-different-environments-generates-different-cdt/145809"]Sorry everyone for not replying but my account is being flagged for spam at each comment i make. I'm afraid of being banned [/quote]

Just to let you know, this is an issue with the software here that happens even to us more experienced users, and the admins are aware of it and, at the very least, manually verify things on their end when they can. Spambots are a major issue here intermittently which is why the settings are so sensitive (AFAIK), but they won't ban anyone who isn't actually a spambot, regardless of whether you trip the automated flags often or not.

RE: Same database view in different environments generates different cdt

Chiara Gambone — Fri, 28 Feb 2025 16:29:18 GMT

Sorry everyone for not replying but my account is being flagged for spam at each comment i make. I'm afraid of being banned so I will just add this.

These are the XSD of the two environments in order

<xsd:element name="abi" nillable="true" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="appian.jpa">@Column(name="ABI", columnDefinition="LONGTEXT")</xsd:appinfo>
</xsd:annotation>
</xsd:element>

In one case I can validate the Data Store without error, in the other case

found [mediumtext (Types#LONGVARCHAR)], but expecting [longtext (Types#VARCHAR)] (APNX-2-4056-000)

But I have know noticed that even with this error in the Data Store, the query entity on this View works, so I won't touch it anymore and hope that in production environment it works.

I have tried dropping the view and recreating it, deleting the xsd and importing again, it's not changing.

RE: Same database view in different environments generates different cdt

Stefan Helzle — Tue, 25 Feb 2025 15:18:02 GMT

OK, and the XSD of the CDT on both environments?

RE: Same database view in different environments generates different cdt

Chiara Gambone — Tue, 25 Feb 2025 14:45:44 GMT

How do you mean Mathieu Drouin ? As you can see the Database shows one thing, but then Appian shows another and I cannot reconcile the two

RE: Same database view in different environments generates different cdt

Mathieu Drouin — Tue, 25 Feb 2025 13:04:00 GMT

Are you sure they are long text in both environnements?

RE: Same database view in different environments generates different cdt

Chiara Gambone — Tue, 25 Feb 2025 10:43:07 GMT

Stefan do you mean the code that generates the View or just the resulting structure? In any case, they appear exactly the same in PhpMyAdmin:

DEV ENVIRONMENT:

Name	Type	Collation	Attributes	Default	Comments
1	ID	int(11)		No	0
2	xx	varchar(255)	utf8mb3_general_ci	Yes	NULL
3	xx	varchar(255)	utf8mb3_general_ci	Yes	NULL
4	xx	varchar(255)	utf8mb3_general_ci	Yes	NULL
5	xx	int(11)		Yes	NULL
6	xx	int(11)		Yes	NULL
7	xx	int(11)		Yes	NULL
8	xx	int(11)		Yes	NULL
9	xx	int(11)		Yes	NULL
10	xx	date		Yes	NULL
11	ABI	mediumtext	utf8mb3_general_ci	Yes	NULL

TEST ENVIRONMENT:

Name	Type	Collation	Attributes	Default	Comments
1	ID	int(11)		No	0
2	xx	varchar(255)	utf8mb3_general_ci	Yes	NULL
3	xx	varchar(255)	utf8mb3_general_ci	Yes	NULL
4	xx	varchar(255)	utf8mb3_general_ci	Yes	NULL
5	xx	int(11)		Yes	NULL
6	xx	int(11)		Yes	NULL
7	xx	int(11)		Yes	NULL
8	xx	int(11)		Yes	NULL
9	xx	int(11)		Yes	NULL
10	xx	date		Yes	NULL
11	ABI	mediumtext	utf8mb3_general_ci	Yes	NULL

When I import you can see it recognizes "longtext"

RE: Same database view in different environments generates different cdt

Stefan Helzle — Tue, 25 Feb 2025 10:32:10 GMT

Can you post that PhpMyAdmin structure from both environments?

RE: Same database view in different environments generates different cdt

Chiara Gambone — Tue, 25 Feb 2025 09:24:00 GMT

This is what I see when trying to update the CDT:

wrong column type encountered in column [ABI] in table [`XXXXXX`]; found [longtext (Types#LONGVARCHAR)], but expecting [mediumtext (Types#VARCHAR)]

This is what i see in MariaDB/PhpMyAdmin:

Name	Type	Collation	Attributes	Default	Comments
1	xxxx	int(11)		No	0
2	xxxxx	varchar(255)	utf8mb3_general_ci	Yes	NULL
11	ABI	mediumtext	utf8mb3_general_ci	Yes	NULL

I don't know where Appian is getting longtext/longvarchar from.

RE: Same database view in different environments generates different cdt

Harsha Sharma — Tue, 25 Feb 2025 08:57:54 GMT

Did you check the source table's column data type is MEDIUMTEX or LONGTEXT in test environment? If the tables are identical between all environments the view will be of identical structure too.