https://bugs.documentfoundation.org/show_bug.cgi?id=128698
Julien Nabet changed:
What|Removed |Added
Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #17 from Commit Notification
---
Julien Nabet committed a patch related to this issue.
It has been pushed to "master":
https://git.libreoffice.org/core/commit/97ad402d58b52a1f2636905137c21298531c2935
tdf#128698:
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
Commit Notification changed:
What|Removed |Added
Whiteboard||target:6.5.0
--
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #16 from Julien Nabet ---
This patch seems to fix it, at least I don't reproduce the pb with it:
diff --git a/connectivity/source/drivers/mysqlc/mysqlc_preparedstatement.cxx
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #15 from Julien Nabet ---
I don't even know where I can see the request which will be executed:
161 int nFail = mysql_stmt_execute(m_pStmt);
(gdb) p m_pStmt
$27 = (MYSQL_STMT *) 0x58d06190
(gdb) p *m_pStmt
$28 =
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #14 from Julien Nabet ---
I gave a new try and this time have 00:00:00 each time.
Trying to debug this, I only can tell that everything seems ok in
"OPreparedStatement::setTime"
(see
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
Xisco Faulí changed:
What|Removed |Added
Assignee|xiscofa...@libreoffice.org |libreoffice-b...@lists.free
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
Xisco Faulí changed:
What|Removed |Added
Priority|highest |medium
Resolution|FIXED
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
erich changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #7 from Robert Großkopf ---
(In reply to erich from comment #6)
> Thanks Robert
>
> I solved (MY) problem (getting up early this morning)
>
> Using Version 6.1.
> testing falling back till 5.7. but
>
> The
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
erich changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #6 from erich ---
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #5 from Robert Großkopf ---
(In reply to erich from comment #4)
> Similar Problem as Alex
> Using a Form entering 12:45 sends a Key Error Time 00:00:00 duplicate key
>
> Entering 12:45 in mysql workbench I find 45:00:00 in
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #4 from erich ---
Similar Problem as Alex
Using a Form entering 12:45 sends a Key Error Time 00:00:00 duplicate key
Entering 12:45 in mysql workbench I find 45:00:00 in my dbase Form
Under debian 9
--
You are receiving
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
QA Administrators changed:
What|Removed |Added
Keywords||bibisectRequest
--
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #3 from Alex Thurgood ---
Something weird going on.
If I change the name of the time field, by opening up the table for edition,
then saving the change, and re-opening the table for data entry, I can now
enter any time I
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
--- Comment #2 from Alex Thurgood ---
The fact that 00:00:00 gets committed to the database, which means data is lost
when editing an existing entry, indicates that an incorrect string is being
passed to the parser to perform the INSERT
https://bugs.documentfoundation.org/show_bug.cgi?id=128698
Alex Thurgood changed:
What|Removed |Added
Summary|MySQL/MariaDB direct|MySQL/MariaDB direct
17 matches
Mail list logo