Submitted by: Leonard Wennekers (l.wennekers)

The migration below will generate an exception on the trigger because of the identify: true inside SequenceId = c.Long(nullable: false, identify: true)
The used name of the trigger ID_HistoryUnknownMessages_SequenceId is not allowed because of it's length.

CreateTable(
"HistoryUnknownMessages",
c => new
{
SequenceId = c.Long(nullable: false, identify: true),
EventOccurred = c.DateTime(nullable: false),
Address = c.String(nullable: false, maxLength: 15),
Message = c.String(nullable: false, maxLength: 1000),
})
.PrimaryKey(t => t.SequenceId, name: "PK_HistoryUnknownMessages");

2016-11-17 09:20:57,105 [TestRunnerThread] DEBUG IOLAN.Context.Management.MigrationLogger - Verbose (): CREATE TABLE "HistoryUnknownMessages" (
"SequenceId" BIGINT NOT NULL,
"EventOccurred" TIMESTAMP NOT NULL,
"Address" VARCHAR(15) NOT NULL,
"Message" VARCHAR(1000) NOT NULL
)
2016-11-17 09:20:57,105 [TestRunnerThread] DEBUG IOLAN.Context.Management.MigrationLogger - Verbose (): ALTER TABLE "HistoryUnknownMessages" ADD CONSTRAINT "PK_HistoryUnknownMessages" PRIMARY KEY ("SequenceId")
2016-11-17 09:20:57,105 [TestRunnerThread] DEBUG IOLAN.Context.Management.MigrationLogger - Verbose (): EXECUTE BLOCK
AS
BEGIN
if (not exists(select 1 from rdb$generators where rdb$generator_name = 'GEN_IDENTITY')) then
begin
execute statement 'create sequence GEN_IDENTITY';
end
END
2016-11-17 09:20:57,105 [TestRunnerThread] DEBUG IOLAN.Context.Management.MigrationLogger - Verbose (): CREATE OR ALTER TRIGGER "ID_HistoryUnknownMessages_SequenceId" ACTIVE BEFORE INSERT ON "HistoryUnknownMessages"
AS
BEGIN
if (new."SequenceId" is null) then
begin
new."SequenceId" = next value for GEN_IDENTITY;
end
END