Arcady Abramov wrote:
Reg Domaratzki wrote:
> I used to get errors when the ml_column collection for the table did not match the remote publication.
I'm not quite sure I understand this comment. Currently, the ml_column collection for the table does NOT match the remote publication for all remote databases. It was my understanding that the only issue you were seeing was data being applied to the incorrect columns, but no actual errors were reported.
Reg
Actually, the column collection itself matches perfectly. It is the order of the columns (apparently, not being checked by the Mobinlink server) that is different.
OK, we're just disagreeing on the definition of "match".
If calls are made to the ml_add_column stored procedure and rows are added to the ml_column table, the MobiLink Server will assume that these are the names of the columns for that table, and the order in which they appear, since that is what it has been told. It will ignore the names of the columns in the uploaded schema if rows exist. If there are no rows in the ml_column table, then the MobiLink Server will use the schema definition that was uploaded by the remote to determine the order and names of columns in the remote database.
Reg