On Jan 30, 2011, at 2:08 AM, Karl Weber wrote:
> Keith Bellairs wrote:
>
>> After a clean build (make clean; make), I cannot replicate the issues with
>> a fresh database. The problems persist for a pg database created in 2.3.17
>> a
>> few builds ago. Given that 2.4 comes out clean, I think th
Keith Bellairs wrote:
> After a clean build (make clean; make), I cannot replicate the issues with
> a fresh database. The problems persist for a pg database created in 2.3.17
> a
> few builds ago. Given that 2.4 comes out clean, I think these are not a
> bug.
>
I downloaded 2.4.0 yesterday and
On Jan 23, 2011, at 12:42 PM, david.vali...@email.cz wrote:
> Hi,
> I face the problem described - (unable to save to database and gnclock not
> cleared) after
> - created a new postgresql database.
> - opened an xml database in gnucash 2.4.0
> - saved it to the postgres database
> - closed , op
Hi,
I face the problem described - (unable to save to database and gnclock not
cleared) after
- created a new postgresql database.
- opened an xml database in gnucash 2.4.0
- saved it to the postgres database
- closed , open again
- trying to make a change in it using Gnucash 2.4.0
I can't find i
On Dec 21, 2010, at 11:28 AM, Keith Bellairs wrote:
> After a clean build (make clean; make), I cannot replicate the issues with a
> fresh database. The problems persist for a pg database created in 2.3.17 a
> few builds ago. Given that 2.4 comes out clean, I think these are not a bug.
>
Rig
After a clean build (make clean; make), I cannot replicate the issues with a
fresh database. The problems persist for a pg database created in 2.3.17 a
few builds ago. Given that 2.4 comes out clean, I think these are not a
bug.
On Tue, Dec 21, 2010 at 1:14 PM, John Ralls wrote:
>
> On Dec 21,
On Dec 21, 2010, at 9:59 AM, Keith Bellairs wrote:
> Since these are not replicated, I'll start with a make clean before I do
> anything else.
>
> On Tue, Dec 21, 2010 at 11:58 AM, John Ralls wrote:
>
> On Dec 21, 2010, at 7:23 AM, Keith Bellairs wrote:
>
> > using a new gnucash db created w
On Dec 21, 2010, at 7:23 AM, Keith Bellairs wrote:
> using a new gnucash db created with r19971 in postgres a few odd things
> happen.
>
> 1. On reopening the db the following notices appear in the output in the
> command prompt window. Are these tables being receated every time?
>
> NOTICE:
took something for it.
From: Keith Bellairs
To: gnucash-devel
Sent: Tue, December 21, 2010 10:23:29 AM
Subject: 2.4 postgres database issues
using a new gnucash db created with r19971 in postgres a few odd things
happen.
1. On reopening the db the following
:29 AM
Subject: 2.4 postgres database issues
using a new gnucash db created with r19971 in postgres a few odd things
happen.
1. On reopening the db the following notices appear in the output in the
command prompt window. Are these tables being receated every time?
NOTICE: CREATE TABLE will
using a new gnucash db created with r19971 in postgres a few odd things
happen.
1. On reopening the db the following notices appear in the output in the
command prompt window. Are these tables being receated every time?
NOTICE: CREATE TABLE will create implicit sequence "recurrences_id_seq1"
fo
11 matches
Mail list logo
