> Hello,
>
> since 3 days during production the modified date does not chenge, is there a
> reason why? Its the right database.
This is a Windows issue, it does not update file properties until a file is
closed. Since, you haven't closed the database file...
Sean
On 11/03/16 13:06, Mark Rotteveel m...@lawinegevaar.nl
[firebird-support] wrote:
> As quoted in the documentation in my previous mail, Windows only guarantees
> updates of the timestamps when the handle is closed.
Which has been the case in windows for 20 years. It is only M$ who could
'fix'
On 2016-03-11 13:40, 'Checkmail' check_m...@satron.de
[firebird-support] wrote:
> Hi,
>
> my third ticked within three days. What should I do, windows ticket?
> E-Mail an microsoft? ;)
It is expected behavior. See
11.03.2016 13:40, 'Checkmail' check_m...@satron.de [firebird-support] wrote:
> What should I do, windows ticket? E-Mail an microsoft? ;)
Yep. That was their decision to save your HDD by not writing modification
time until
the file is closed.
--
WBR, SD.
] timestamp of the firebird database
(modified date) does not change in fb 3.0 RC2
> 11.03.2016 12:59, liviuslivius liviusliv...@poczta.onet.pl
> <mailto:liviusliv...@poczta.onet.pl> [firebird-support] wrote:
> > i can confirm this - database modified datatime is
11.03.2016 12:59, liviuslivius liviusliv...@poczta.onet.pl [firebird-support]
wrote:
> i can confirm this - database modified datatime is frozen when first
> connection has started.
> i suppose that you should raport ticket into the firebird tracker.
This ticket rather belongs to Windows
Hello,
since 3 days during production the modified date does not chenge, is there a
reason why? Its the right database.
Thanks.
Hi,
i can confirm this - database modified datatime is frozen when first connection
has started.
i suppose that you should raport ticket into the firebird
Hello,
since 3 days during production the modified date does not chenge, is there a
reason why? Its the right database.
Thanks.