<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Firebird: Migration: Time values are being changed during migration process (data type TIME and DATETIME)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=117732#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Firebird: Migration: Time values are being changed during migration process (data type TIME and DATETIME)"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=117732">bug 117732</a>
from <span class="vcard"><a class="email" href="mailto:btomi96@gmail.com" title="Tamas Bunth <btomi96@gmail.com>"> <span class="fn">Tamas Bunth</span></a>
</span></b>
<pre>(In reply to Drew Jensen from <a href="show_bug.cgi?id=117732#c22">comment #22</a>)
<span class="quote">> Does anyone think that the correct way would be to use the current OS TZ
> informtion when the migration assistant to change the data so what the user
> sees in the Base UI is the same before and after migration?</span >
I think it would make sense letting the user decide that. I would suggest a
pop-up dialog right after the user pressed "yes, I want to migrate". This
dialog would appear only if the database contains TIME, DATE, or DATETIME data
types, and it would ask the user if he wants to interpret his data as (UTC+0)
or he would prefer the recalculation of data using OS timezone information.
<span class="quote">> It is not a big deal to change the values, with a four step process, add
> column, move data with offset fixup, drop the old column, rename the new one
> to match the old. (of course there is any optional steps of dropping and
> recreating things like views and relations that might of used those old
> columns..but) - but big enough that I can easily bet that some of the users
> who would of voted yes above are not going to be happy about that as a
> solution - even with clear examples of how to do it. (which I would be
> willing to put together)</span >
I agree. A built-in solution is better (like the suggestion above) than a wiki
page describing what to do.
I would suggest to create a new bug report marked as feature request with the
above changes and close this bug as "won't fix" or "moved"</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>