Bug 143850 - Gnucash does not store clients or their jobs
Gnucash does not store clients or their jobs
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: gnucash (Show other bugs)
3
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-12-29 19:48 EST by Xander D Harkness
Modified: 2016-06-07 18:45 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-29 19:57:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Xander D Harkness 2004-12-29 19:48:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
I try to create a new customer with all details, email address, name etc.

I can add jobs and invoices to this customer.

If I close gnucash and start it again, I have no customers.

Version-Release number of selected component (if applicable):
gnucash-backend-postgres-1.8.9-2 gnucash-1.8.9-2

How reproducible:
Always

Steps to Reproduce:
1. Start gnucash with the following argument: gnucash
postgres://ipaddress/database?mode=multi-user
2.Create a new customer with all required details
3. Close gnucash
4. Start Gnucash and there are no customers
    

Actual Results:  On the console I get the following errors and no
customers:
Error: sqlQuery_build: Only SPLITs are supported, not gncCustomer
Error: pgendFillOutToCheckpoint: send query failed:
        command string is a null pointer


Expected Results:  Gnucash should create a customer and allow me to
add jobs.

Additional info:

This also occurs when I do not use multi-user mode.
Comment 1 Bill Nottingham 2004-12-29 19:57:56 EST
Reported upstream at:

http://bugzilla.gnome.org/show_bug.cgi?id=162502

Realistically, this isn't something we'll fix inhouse.

Note You need to log in before you can comment on or make changes to this bug.