On Wednesday December 8 2010 20:48:32 Derek Atkins wrote:
> Mike Evans writes:
> >> Why did you remove -Werror?
> >>
> >> -derek
> >
> > Ah. I wanted to enable SWIG %feature("autodoc", "1"); to make debugging
> > easier. Compile fails with an error if -Werror in enabled. I forgot to
> > put i
On Wednesday 08 December 2010, Christoph Holtermann wrote:
> Hello !
>
> It surely would be useful to have some more documentation to the
> python bindings. I can imagine to write some things I understand when
> figuring out how things work if I see that the feature is not documented.
> I wonder
Hello !
I just found the documentation for a perl skript calles gnc-prices [1]. It
seems to me that it doesn't exist anymore. Maybe the documentation
can be deleted then ?
regards,
Christoph Holtermann
[1] http://www.linuxmanpages.com/man1/gnc-prices.1.php
in the source tree : doc/gnc-prices.1
John Ralls writes:
>> Maybe this is a silly question, but why couldn't we use the versions
>> table to notice this, too? It's still a bug in the SQL, and we should
>> get used to fixing SQL bugs internally.
>>
>> I understand it might take a few tries to get right, but that's what
>> "mysqldump
Hi,
Mike Evans writes:
> With %feature("autodoc", "1"); and -Werror I get:
>
> ../../../src/engine/Account.h:182: Warning(314): 'from' is a python keyword,
> renaming to '_from'
> ../../../src/libqof/qof/gnc-numeric.h:266: Warning(314): 'in' is a python
> keyword, renaming to '_in'
> ../../../
On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
> John Ralls writes:
>
>
>> Oh, and there isn't enough sql yet to have "bugs in the sql".
>
> The fact that we're having this discussion would prove this incorrect.
> There already has been a bug in the SQL causing the slots to not get
> delete
On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
>
> Let's get 2.4 out the door first, and then we can talk about how we can
> fix this in a piecemeal fashion. It would be nice if we could get
> releases out approximately yearly. Can we come up with a
> feature-set/timeline that would allow for
On Thu, December 9, 2010 12:01 pm, John Ralls wrote:
>
> On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
>
>> John Ralls writes:
>>
>>
>>> Oh, and there isn't enough sql yet to have "bugs in the sql".
>>
>> The fact that we're having this discussion would prove this incorrect.
>> There already has
On Dec 9, 2010, at 7:05 AM, Derek Atkins wrote:
> John Ralls writes:
>
>> But we could add a row to the versions table with the last Gnucash
>> version to touch the database. When we write a change to the backend
>> that changes the way data are stored, we can invoke a routine that
>> reads eve
Hello !
I read this just now. Report generation, moving transactions according to
name criteria are all things that can quite easily be done with the python-
bindings. They're actually quite a source of joy ;-) Momentarily you just
have to fall in love with svn, too and build gnucash from source
--On December 9, 2010 10:24:51 AM -0800 John Ralls
wrote:
Anyway, if we're going to introduce the gnucash-version row, we
should do it now, before 2.4 is released.
It seems like this is a good idea, even if it is never used for
automatic upgrades or fixups. At the very least it would help
Am Mittwoch, 8. Dezember 2010 um 20:46:25 schrieb Derek Atkins:
> Geert Janssens writes:
> > On Tuesday 07 December 2010, John Ralls wrote:
> >> Schema: OK. To make the policy clearer, backwards-incompatible schema
> >> changes in 2.5 require a change to 2.4 to provide a read facility for
> >> the
Hi,
Using this excerpt as a context:
Message: 1
Date: Tue, 7 Dec 2010 09:33:58 -0800
From: John Ralls
Subject: Re: close books
To: Derek Atkins
Cc: devel gnucash
Message-ID: <2b1f2747-854c-430c-8aaa-05637e30a...@ceridwen.us>
Content-Type: text/plain; charset=us-ascii
[...]
A KVP *is* bette
On Dec 9, 2010, at 1:10 PM, Thomas Bullock wrote:
> Hi,
>
> Using this excerpt as a context:
>
> Message: 1
> Date: Tue, 7 Dec 2010 09:33:58 -0800
> From: John Ralls
> Subject: Re: close books
> To: Derek Atkins
> Cc: devel gnucash
> Message-ID: <2b1f2747-854c-430c-8aaa-05637e30a...@ceridwen
On Thursday 09 December 2010, Frank H. Ellenberger wrote:
> Am Mittwoch, 8. Dezember 2010 um 20:46:25 schrieb Derek Atkins:
> > Geert Janssens writes:
> > > On Tuesday 07 December 2010, John Ralls wrote:
> > >> Schema: OK. To make the policy clearer, backwards-incompatible schema
> > >> changes in
Is it normal for the Check & Repair All command to generate a log file 25x the
size of my original XML datafile? I was having problems with very slow loading
of my data file, so I ran Check & Repair All a couple of different times, and
all of a sudden the partition holding the data file reached
16 matches
Mail list logo
