Sure! Thank you for being willing to try new things. We are glad to help
you learn, because more hands are better.
The right direction is the link on the main GnuCash.org page, left
column, under "Support", labelled "Bug Reports". It points to an
introduction page, <https://wiki.gnucash.org/wiki/Bugzilla
<https://wiki.gnucash.org/wiki/Bugzilla>>. Give that a read.
You may find that some of the instructions there are not clear. In that
case, you can either improve the page yourself — it is a wiki; or report
problems in this email thread, and we'll help you along. You may help us
find where /we/ want to improve the instructions.
Don't worry if the bug report isn't perfect. Do your best, and then
others can come in and polish it. The main thing is to make a record
that the problem exists.
Thank you, Gord!
—Jim DeLaHunt
On 2021-02-02 13:27, gnu Gord wrote:
I would be happy to open a bug report but I have no idea how to do it.
Can you point me in the right direction?
On Mon, Feb 1, 2021 at 7:25 PM Jim DeLaHunt <list+gnuc...@jdlh.com
<mailto:list%2bgnuc...@jdlh.com>> wrote:
Good catch, Gord!
On 2021-02-01 10:36, gnu Gord wrote:
> …It appears that mysql (or somewhere in the backend of gnuCash)
does not
> like a back slash character as the last character in a field.
The data I
> was trying to save had one entry with a 'notes' field that … was
> "2 books one for A one for\".…
>
> Here are the relevant lines from the 'gnucash.trace' file:
>
> * 09:09:43 ERROR <gnc.backend.dbi> [error_handler()] DBI error:
1064: You
> have an error in your SQL syntax; check the manual that
corresponds to your
> MariaDB server version for the right syntax to use near '1970-01-01
> 00:00:00',0,1)' at line 1
> * 09:09:43 ERROR <gnc.backend.dbi>
> [GncDbiSqlConnection::execute_nonselect_statement()] Error
executing SQL
> INSERT INTO
>
slots(obj_guid,name,slot_type,int64_val,string_val,timespec_val,numeric_val_num,numeric_val_denom)
> VALUES('c4f3c08454534822a2ff8cbb662b44cf','notes',4,0,'2 books
one for A
> one for\','1970-01-01 00:00:00',0,1)
> * 09:09:43 ERROR <gnc.backend.sql>
> [GncSqlBackend::execute_nonselect_statement()] SQL error: INSERT
INTO
>
slots(obj_guid,name,slot_type,int64_val,string_val,timespec_val,numeric_val_num,numeric_val_denom)
> VALUES('c4f3c08454534822a2ff8cbb662b44cf','notes',4,0,'2 books
one for A
> one for\','1970-01-01 00:00:00',0,1)
> * 09:09:43 ERROR <gnc.backend.sql> [GncSqlTransBackend::commit()]
> Transaction Chapters dated 2011-02-21 in account Gifts not saved
due to
> Slots save failed. Check trace log for SQL errors.
I encourage you to write a bug report in the GnuCash bug tracker
about
this problem. As a general matter, GnuCash should not let any text
you
type into a Notes field turn into a syntax error for the database. It
should wrap the Notes text in a way that prevents the syntax error
from
happening. I suspect that GnuCash does this kind of wrapping the
XML way
if the backend is XML, but doesn't do it the SQL way if the
database is SQL.
It's good to have people turn up errors with nice solid evidence like
you collected. Thanks!
Best regard,
—Jim DeLaHunt
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org>
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
<https://lists.gnucash.org/mailman/listinfo/gnucash-user>
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists
<https://wiki.gnucash.org/wiki/Mailing_Lists> for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
