[11.5.362 Pro] - Predicted table structure glitch (MariaDB)

[11.5.362 Pro] - Predicted table structure glitch (MariaDB)

There's a minor glitch when displaying the predicted table structure for a table (hover on) that has been/will be created using the CREATE TABLE ... AS SELECT... statement. Check this short video here.

I'm joining two tables and explicitly list all the columns I want the new table to have. However, when I hover the mouse cursor over the newly created table, SA displays the tooltip showing all the columns from the first table in the join and none of those from the second one. Moreover, it keeps its (otherwise wrong) opinion about the columns even after creating the table but that's at least consistent with the prediction. It's great that it recognizes that the table will probably change and it tries to show its future state instead of the current, unfortunately, it guesses that state incorrectly.

I'm reposting here to confirm that this issue has been reproduced by our team and I submitted a defect for it to fixed. The defect number is #SA0041638. Hopefully it is going to be fixed soon.

Also moving here my follow up message which I accidentally entered in a different topic

	Quote:
	Just in case, if you have a table declared in script, a table variable, or CREATE TABLE DDL, the intellisense always uses definition given in the script over definition of the existing table in the database. If a temporary table is created using other SQL, like CREATE TABLE ... AS SELECT ..., or SELECT ... INTO #temp_table, then it attempts to recognize how that table may look like in ruin-time.