Thank you for the note Ian. I definitely see your point about the onus being on the local database to maintain the definition of the remote table. Do you or anyone have this list have any experience with the resulting behavior if the definition of the enum were to become out of sync between the local database and the foreign database? In other words, suppose the foreign database adds a value to the enum, and the foreign table now has rows with this new value, while the local definition of the enum remains unchanged. Obviously, the appropriate action on my part is to maintain consistency of enum definition between the foreign and local database, but I'm curious about what behavior would result if there was an error in this manual updating process.
I may dig into this a bit further myself in a few test databases, to see what happens. Will post a response if I do.
With regards,
