_id column when working with external SQL DB has encoded id value

[poirazis]

When you query a table that is an external sql table, you always get back a column "_id" ammended, but the value in that column is not the value of the id, but rather a string encoded. So , if you attemp to update / delete record using that "_id" added column, the operation will fail as that column doesnt actually exist nor the value in it represents the actual id.

This ammended column, also appears in the "field" property types, to be selected.

Is this ammeded column necessary ?
If it is, shouldnt it be holding the same value as the id column ?

[linear]

BUDI-8784 _id column when working with external SQL DB has encoded id value

[mike12345567]

Hi @poirazis - this is intended functionality - Budibase needs the _id field to be completely unique, in the case of tables with composite primary keys the only real way to handle this is encoding the contents into a consistent format that we can understand.

Having multiple formats for this can be quite tricky, so we decided that we should always encode it to follow a consistent format that we can expect no matter if the table has a composite key or not.

I'm going to close out this issue as a change in this area would be quite dangerous and this is fully intended behaviour - if it is causing a problem in the app building experience, please let us know with an enhancement request around the behaviour that it is causing issues with!