Re: [Firebird-devel] Unique constraint and timezones and changes

2021-02-25 Thread Jiří Činčura
> If you rebuild the index, there will be no such problem, because the > date is stored in UTC, so that will not have changed. Yeah, silly me. Obviously the timezone info isn't lost when converting to UTC and storing in index. What was I thinking??? 🤷‍♂️ -- Mgr. Jiří Činčura https://www.tabsov

Re: [Firebird-devel] Unique constraint and timezones and changes

2021-02-25 Thread Mark Rotteveel
On 2021-02-25 19:55, Jiří Činčura wrote: Could you describe the scenario you're thinking of that you think could be problematic. Well, I was mostly thinking what would happen is suddenly some dates become colliding in UTC in i.e. unique index and you rebuild the index. It was fine before, but

Re: [Firebird-devel] Unique constraint and timezones and changes

2021-02-25 Thread Jiří Činčura
> Could you describe the scenario you're thinking of that you think could > be problematic. Well, I was mostly thinking what would happen is suddenly some dates become colliding in UTC in i.e. unique index and you rebuild the index. It was fine before, but it's not now. But it could be also so

Re: [Firebird-devel] Unique constraint and timezones and changes

2021-02-25 Thread Mark Rotteveel
On 2021-02-25 13:52, Jiří Činčura wrote: Hi *, for the unique constraint the times are equivalent if the UTC time is equivalent. How's this going to be handled when some timezone region changes its offset and the UTC time becomes the same? The value stored is in UTC and remains in UTC, so time

[Firebird-devel] Unique constraint and timezones and changes

2021-02-25 Thread Jiří Činčura
Hi *, for the unique constraint the times are equivalent if the UTC time is equivalent. How's this going to be handled when some timezone region changes its offset and the UTC time becomes the same? -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ Firebird-Devel mailing list, web interfa