On 18 Dec 2000 13:00:56 EST, the world broke into rejoicing as
Derek Atkins <[EMAIL PROTECTED]> said:
> Christopher Browne <[EMAIL PROTECTED]> writes:
> > It shouldn't be a situation of the GUI submitting database queries;
> > instead, the GUI should submit _transaction_ queries to the engine, an
had a chance to consider how adding the ability to calculate
totals to the Query API might work?
Anyway, I'm pleased to have this working, and as soon as Rob and I
sort out a new g-wrap release I'll send out the patch.
-
>
> Are you saying that I should NEVER have multiple lines of a split transaction
> which "duplicate" other lines of the transaction?
I was talking about something else entirely. But thanks for the excellent
example that illustrates the problem.
If you use the find dialog, and search on "INCOM
On Fri, 21 Apr 2000, Bryan Larsen wrote:
> I've run up against the exact same problem in the "transactions 2" report.
> I haven't done anything about it, but it was my opinion that duplicates
> should only be removed if:
> 1) in a multi-line report format, and
> 2) are in the same subsection.
>
On Fri, 21 Apr 2000, Dave Peticolas wrote:
> > Bryan Larsen <[EMAIL PROTECTED]> writes:
> > > 2. Transactions can appear more than once. That seems pretty durn wacky.
> >
> > Dave: what did we decide about this? Is it a problem with the Split**
> > I am generating, or a natural side effect of t
> Bryan Larsen <[EMAIL PROTECTED]> writes:
> > 2. Transactions can appear more than once. That seems pretty durn wacky.
>
> Dave: what did we decide about this? Is it a problem with the Split**
> I am generating, or a natural side effect of the way the register
> works? I remember that discuss
> There's support for user-provided query predicates, which I engineered
> with Scheme in mind; if you have a user filter-pred that's a scheme
> thunk, it's possible to add it to queries also. I just need to write
> a little C wrapper to call it.
>
I definitely don't need this, as the find dial
Bryan Larsen <[EMAIL PROTECTED]> writes:
> 2. Transactions can appear more than once. That seems pretty durn wacky.
Dave: what did we decide about this? Is it a problem with the Split**
I am generating, or a natural side effect of the way the register
works? I remember that discussion about re
OK, I've been playing with the new find dialog.
1: it really highlights something that's bothered me for a long time about the
register: the fact that, for a multi-line display, the first line displays the
amount in the wrong column. Before you could put up with it, because you knew
what accou
