-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Gribble wrote:
>
> On Sat, Jul 29, 2000 at 01:30:05PM +0100, Steven Murdoch wrote:
> > It seems clear to me that there are many occasions where a value
> > is stored, and it's only permissable values are integers (things
> > like number of share
On Fri, 28 Jul 2000, you wrote:
>
> Unfortunately, all Bill has provided is a way of representing and
> manipulating rational values. There's nothing particularly _wrong_ or
> awful about having that. I don't think we need to go so far as to burn
> the proposal, strew the ashes in a field, and
On Fri, 28 Jul 2000, you wrote:
> > I haven't seen a
> > similar single discription and corresponding implementation on your
> > proposal.
>
> I haven't made it in that form because it is too trivial.
That should make it easier to put down so that others can review it, comment on
it, improve on
Hi,
I've been starting to make some performance
improvments to gnucash. As background, I have a .xac
file of about 1.5MB (10 years of transactions) so
there are some things where it is quite slow (like
loading and exiting). The following patches are based
on the current CVS tree but ap
> My question is would it be *easier* to implement the modifications
> needed to Gnucash if another type and it's associated funcions were
> added to the API that could only represent integers (say stored as a
> 64bit integer)?
>
Using 64 bit integers is a very powerful approach. I posted a note
On Sat, Jul 29, 2000 at 04:57:53PM +0100, Keith Refson wrote:
> What do you have in mind for the full facility? A near-miss match
> with a query window?
My current thought is that we'd have a two-column window that's a
distant cousin of the reconcile window. For each imported transaction
(possi
Bill Gribble writes:
> The kind of duplicate detection you are looking for is in the feature
> list for the next revision of the QIF importer. It's a little
> trickier, because the fields describing the transaction are often very
> different (comparing a hand-entered transaction to a downloa
On Sat, 29 Jul 2000, Bill Gribble wrote:
> The kind of duplicate detection you are looking for is in the feature
> list for the next revision of the QIF importer. It's a little
> trickier, because the fields describing the transaction are often very
> different (comparing a hand-entered transact
On Sat, 29 Jul 2000, Bill Gribble wrote:
> On Sat, Jul 29, 2000 at 01:30:05PM +0100, Steven Murdoch wrote:
> > It seems clear to me that there are many occasions where a value is
> > stored, and it's only permissable values are integers (things like
> > number of shares, bank balance, number of ac
On Sat, Jul 29, 2000 at 02:26:53PM +0100, Keith Refson wrote:
> I am currently running 1.43. When I import a qif file from my online
> bank which contains transactions already in the gnucash record, the
> duplicates are not detected and the transactions are recorded twice.
>
> Am I correct in un
On Sat, Jul 29, 2000 at 01:30:05PM +0100, Steven Murdoch wrote:
> It seems clear to me that there are many occasions where a value is
> stored, and it's only permissable values are integers (things like
> number of shares, bank balance, number of accounts etc...). Bill's API
> is clearly sufficien
I am currently running 1.43. When I import a qif file from my online
bank which contains transactions already in the gnucash record, the
duplicates are not detected and the transactions are recorded twice.
Am I correct in understanding that the qif importer is supposed to
eliminate duplicates?
It seems clear to me that there are many occasions where a value is
stored, and it's only permissable values are integers (things like
number of shares, bank balance, number of accounts etc...). Bill's API
is clearly sufficient for this purpose and already has the required
functions to accomodate
13 matches
Mail list logo
