I got a call from the person carrying out the task last night. ExportDDL isn't available in the 2018 Cache version being used. We ended up extracting the DDL though via the external WinSQL software.
What I was looking for was a way to, in effect, swap which member was primary and which was backup. Taking your advice and re-reading the Automatic Failover Mechanics section of the docs I've decided that there is no need for my test.
I took a different approach. I overrode the .close() method at the browser with one that uses #server to send the "I'm closing" message to the Cache server. The message handler at the server then executes the EndServer method in the web socket class.
At the server the web socket class' Server method executes quitting with $$$OK the OnPostServer method does not execute.
Closing the connection from the server end by invoking the web socket object's EndServer method results in the OnPostServer method executing.
Maybe of importance, the websocket is asynchronous so when triggered from the browser's .close() the Server method is not invoking the EndServer method.
go to post
Good afternoon Alexander,
We tried that. It didn't yield the Create Table ddl.
Dan
go to post
Hi Eduard,
I got a call from the person carrying out the task last night. ExportDDL isn't available in the 2018 Cache version being used. We ended up extracting the DDL though via the external WinSQL software.
Thanks again.
go to post
Thanks Eduard. I passed the info along to the person with the task. I'll let you know how well it works for the goal.
Plus, for the task at hand, only the data definitions are necessary, not the data.
go to post
That would be funny if it weren't so true.
This one is very high profile and joins the list of demands competing for resources.
go to post
Hi Robert,
Seeing as how I'm fighting the same issue (keeping mirror members synched, not code DBs though), what does the "Red Fire Button" refer to?
Thanks,
Dan
go to post
Thanks Pete.
I read the first 4 words of your reply and the heel of my hand slapped my forehead; I knew that. It works now. Again, many thanks.
Dan
go to post
Thanks Vic,
What I was looking for was a way to, in effect, swap which member was primary and which was backup. Taking your advice and re-reading the Automatic Failover Mechanics section of the docs I've decided that there is no need for my test.
Thanks again.
Dan
go to post
Loop backwards from the tail to the head.
go to post
Thanks again Aohan.
I took a different approach. I overrode the .close() method at the browser with one that uses #server to send the "I'm closing" message to the Cache server. The message handler at the server then executes the EndServer method in the web socket class.
go to post
Thanks Aohan but still nothing.
At the browser I trigger ws.close()
At the server the web socket class' Server method executes quitting with $$$OK the OnPostServer method does not execute.
Closing the connection from the server end by invoking the web socket object's EndServer method results in the OnPostServer method executing.
Maybe of importance, the websocket is asynchronous so when triggered from the browser's .close() the Server method is not invoking the EndServer method.