[Firebird-devel] Cases when DROP INDEX DDL triggers should be called

[Ilya Eremin]

Hello!

In FB3+, when I create an index on a table's field and then drop this 
table, DROP INDEX DDL triggers are not called. Is it done this way on 
purpose? I did not find a clear description of such case in the 
documentation.


--
Ilya Eremin



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Re: [Firebird-devel] Tablespaces proposal

[Ilya Eremin]

Hello!
The last tablespaces proposal says:
> Tablespaces are excluded from replication because it's physical layout
> of a database and a replica may have another one.

which means that tablespaces-related DDL operators won't be executed on 
a replica. But some conflicts may happen, for example, when a table is 
being moved to another tablespace via ALTER TABLE SET TABLESPACE. If the 
tablespace doesn't exist in a replica, the statement will fail. The 
tablespace should be created in a replica before the statement is executed.


It is possible to do it in another way: replicate tablespaces-related 
DDL to have the same set of tablespaces in a replica. The main problem 
here is the path to a tablespace file. It still can be absolute (will 
work if the path is also valid for a replica) or relative. It might be 
helpful to use directory aliases which can be set in some configuration 
file. And this is a downside - need to edit the configuration file on a 
replica(s).
Which way is better for default behaviour? Would be good to hear 
opinions on this.


--
Ilya Eremin



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] ON DISCONNECT triggers and MON$ATTACHMENTS

[Ilya Eremin]

Hello!

Currently ON DISCONNECT triggers are not called when an attachment is 
deleted from MON$ATTACHMENTS by another attachment. Is it the correct 
behavior? Was it implemented this way on purpose?


--
Ilya Eremin



Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

[Firebird-devel] [FB-Tracker] Created: (CORE-6144) Inconsistent behaviour of the NEW context variable in AFTER UPDATE OR DELETE triggers

[Ilya Eremin (JIRA)]

Inconsistent behaviour of the NEW context variable in AFTER UPDATE OR DELETE 
triggers
-

 Key: CORE-6144
 URL: http://tracker.firebirdsql.org/browse/CORE-6144
 Project: Firebird Core
  Issue Type: Bug
  Components: Engine
Affects Versions: 2.5.9, 4.0 Beta 1, 3.0.4
Reporter: Ilya Eremin


Script to reproduce:

create table test (id integer not null primary key);
commit;
insert into test (id) values (1);
commit;
alter table test add v integer default 1 not null;
commit;
insert into test (id) values (2);

create exception ex 'Failed';

set term ^;

create or alter trigger test_null for test
after update or delete
as
begin
  if (new.v is not null) then -- new.v should be NULL if the trigger runs after 
DELETE statement
exception ex;
end^

set term ;^

commit;

delete from test where id = 2; -- no errors
delete from test where id = 1; -- trigger throws exception


I am working on a PR.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel