>> so I would
>> need to rewrite that to (current_date+current_time) (I can't use
>> CURRENT_TIMESTAMP(0) because I need to be sure that my application work
>> with both Firebird 1.5 and 2.1). That is possible, of course, but it
>> will not help me much if someone (a DB administrator accidentally uses
>> 'now' in a query because, simply because he is used to write 'now'
>> rather than the other method).
>>
> Do you realise that 'NOW' and CURRENT_TIMESTAMP are not the same?
>

The difference is negligible for me.

>> 2. What I actually need is a DATE/TIME datatype which uses a seconds
>> precision. As far as I know, Firebird doesn't have one so I am forced to
>> use TIMESTAMP, which worked fine in Firebird 1.5 but is too precise for
>> my needs in Firebird 2.1.
>>
> You could put in a feature request. I wouldn't hold my breath though: you are asking to have a fixed bug deliberately regressed! Unfortunately for you, it has *never* been a good idea to design a known bug into your code. As is often said, "some day it will bite you."
>

Eh? I am not aware of any bug. Just that I need a particular precision
and apparently am out of luck because there isn't any reasonable way to
reach it.

Never mind. I will simply have to either jump the hoops to get around
it, or decide to stick to Firebird 1.5. The latter course seems to be
preferable - there isn't anything that I actually _need_ from Firebird
2.1, it just has some features which would be nice to have but not
essential.

Pepak