Smalltalk › Gemtalk › GLASS

Monticello and auto-commit

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Sebastia Van Lacke

Monticello and auto-commit

Hi, I have one question about montincello and auto-commit mode. I've tryed to load a package with auto-commit and auto-migrate mode disabled, and I have seen that monticello commits anyway. It doesn't check the commit mode. Is there any way to prevent monticello from commiting?

Thanks

Sebastian

Dale Henrichs

Re: Monticello and auto-commit

Sebastian Van Lacke wrote:
> Hi, I have one question about montincello and auto-commit mode. I've tryed to load a package with auto-commit and auto-migrate mode disabled, and I have seen that monticello commits anyway. It doesn't check the commit mode. Is there any way to prevent monticello from commiting?
>
> Thanks
>
> Sebastian
>

Sebastian,

I read through the code and I couldn't find a spot where a commit would
occur when autoCommit is false. That doesn't mean it can't happen, just
that it's not obvious.

So, if you set a breakpoint in System class>>commitTransaction (after
turning off autoCommit) and then do the load, we should be able to catch
the offending code read handed ... just send me the stack...

Dale

Sebastia Van Lacke

Re: Monticello and auto-commit

In reply to this post by Sebastia Van Lacke

Thanks Dale,

I've tryed to put a breakpoint in commitTransaction method, but I get an error when I want to save the method:

"No authorization to set the current segment to aSegment, Number 1 in Repository SystemRepository, Owner SystemUser write, World read."

Sebastian

Dale Henrichs

Re: Monticello and auto-commit

Sebastian Van Lacke wrote:
> Thanks Dale,
>
> I've tryed to put a breakpoint in commitTransaction method, but I get an error when I want to save the method:
> "No authorization to set the current segment to aSegment, Number 1 in Repository SystemRepository, Owner SystemUser write, World read."
>
> Sebastian
>
That's the error you get when you try to save the method.

Use the 'set breakpoint' menu item in the text pane of the System
browser to set a breakpoint without editing the method. After setting a
breakpoint you can clear individual breakpoints or all of the breakpoints.

Dale

Sebastia Van Lacke

Re: Monticello and auto-commit

In reply to this post by Sebastia Van Lacke

Sorry Dale, I coud set a brekpoint from the menu. I was trying to put a #halt.

I've loaded a package and there was not commit, maybe the auto migrate was set when I trayed it the first time. In that case a commit is executed after migration.

What hapens if I have both disabled and a migration is requiered,Will I need to migrate it myself?

Thanks!

Sebastian

Dale Henrichs

Re: Monticello and auto-commit

Sebastian Van Lacke wrote:

> Sorry Dale, I coud set a brekpoint from the menu. I was trying to put a #halt.
>
> I've loaded a package and there was not commit, maybe the auto migrate was set when I trayed it the first time. In that case a commit is executed after migration.
>
> What hapens if I have both disabled and a migration is requiered,Will I need to migrate it myself?
>
> Thanks!
>
> Sebastian
>

If you have autoCommit disabled, autoMigrate is automatically disabled,
since commits are required to do a migration.

So if you have autoMigrate disabled, no migrations occur at all and you
are expected to do the migration yourself (or arrange to refresh instances).

Dale