Hi,

I use Flamerobin myself and it's always required explicit commits after
DDL statements. However, recently I discovered a convenient option (look
at the "SQL Editor" branch in Flamerobin's preferences) "Automatically
commit DDL statements", which does the trick. I admit I've no idea how
long the option's been there (my ignorance sometimes scares me) but it's
there and does what it says.
So, with the option unchecked, the script

create table T (
F integer
);

create index I on T(F);

fails on create index, saying table "T" doesn't exist. When you put
comimt after create table and before create index, it works.
With the option mentioned above turned on, the commit is issued
automatically by Flamerobin.
The auto-commit is client-dependent. Long ago I used SQL Explorer
shipped with Delphi 4 and it could be told to auto-commit all (!)
statements.

I hope that helped a little.
regards
Tomasz

On 2011-11-18 16:03, martin.agren wrote:
> Hi,
>
> If this is already discussed and answered my apologies.
>
> I leaped from 1.5 to 2.5 and I am generally very happy with the switch.
> There is however one thing driving me crazy.
>
> When I work with DDL in stored procedures (this is where I noticed it so far but I guess it applies to other metadata changes as well), my updates are not reflected consistently in subsequent queries. To make sure they are in scope I have to disconnect my client tool (Flamerobin) and other applications. It seems the DDL changes are in som kind of trasaction control.
> It is however NOT sufficient to commit the active transaction and start a new.
>
> Thanks,
>
> Martin
>
>
>


--
__--==============================--__
__--== Tomasz Tyrakowski ==--__
__--== SOL-SYSTEM ==--__
__--== http://www.sol-system.pl ==--__
__--==============================--__