Same table name cannot exist in different database instances

[Arvydas]

Hello community,

I have an issue: I have 2 different database instance, which both includes same name of the table:
elvi_vom.vendor_order and elvi_vos.vendor_order.

While trying to sync the field of the table, I am not getting proper outcome.

elvi_vom.vendor_order table scans all the field from elvi_vos.vendor_order and because of that users cannot simply create questions from elvi_vom.vendor_order and getting errors:

Because this field is scanned not from elvi_vom.vendor_order but from elvi_vos.vendor_order and it only exists in elvi_vos.vendor_order (not in elvi_vom.vendor_order).

How I could solve this stupid error?
For me it clearly looks like a bug.

Thank you!

[Arvydas]

After triggering Sync Data Schema Now I see in logs this line:

[fec5b062-ca78-4960-a754-8600cf9436b9] 2024-11-22T10:55:03+02:00 INFO metabase.sync.sync-metadata.fields.sync-instances Marking Field ''Table 60 ''vendor_order'' Field 'external_order_data''' as inactive.

But it does not change anything. Still this field is there...

[Arvydas]

After restarting Metbase container --> Update to the latest version --> creating a dummy DB instance (same as existing but with different name) solved my issue on the original DB instance as well.
Strange...

[Luiggi]

we fixed this issue in the latest release