Hello.

I am testing on FrontBase as well and got into some problems with add/ drop not null constraints in the merge stuff. For dropping a not null constraint, you need to create a view for a system table, join ~4 views from some information tables, and then issue some alter table statements.

So for this single merge-token, I need at least two steps to the database. The result of the first step, the constraint name, will then be used to create the second statement. I have not included support for several roundtrips in a single merge-token, so this is kind of hard.

A FrontBase guy sent me a stored procedure for this that does all of that in a single step, but I do not know the license issues involved in using that code. Should I create a jira and ask him to post the procedure there? Will that be enough?

Regards,
 - Tore.

Reply via email to