On 31/10/2012 08:17, Alex Peshkoff wrote:
> On 10/31/12 13:39, Adriano dos Santos Fernandes wrote:
>> On 31/10/2012 07:21, Alex Peshkoff wrote:
>>> Returning to initial problem.
>>> Do we suppose to
>>> create /*for example*/ trigger on create table or alter exception or
>>> drop role?
>>> If yes, bitmask encoding in int64 makes sense.
>> This is what it does:
>>
>> <ddl event> ::=
>> ANY DDL STATEMENT
>> |<ddl event item> [{OR<ddl event item>}...]
>>
>> <ddl event item> ::=
>> CREATE TABLE
>> | ALTER TABLE
>> | DROP TABLE
>> | CREATE PROCEDURE
>> ...
>>
> I understand very well that it's a dirty hack (the only excuse is that
> dialect 1 is a hack itself), but what about having 2 32-bit fields in
> ODS12? In ODS13 we will remove that hack.
>
>
I'd prefer to hack on allowing BIGINT on dialect 1 than do this and deal
with its consequences (gbak, isql, third party clients) later.
Adriano
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
