Custom Reports and Backup

Derek Atkins warlord at MIT.EDU
Mon Jun 8 11:04:44 EDT 2009


"Colin Scott" <gnucash at double-bars.net> writes:

>> This is an interesting idea, but fundamentally flawed in that while 
>> account definition might be abstracted to a certain extent, 
>> ultimately, a programmer cannot be certain about ANY specific 
>> accounts in a file.
>
> I think you may have misunderstood where I was going.  I was suggesting a
> way that *the user* might define the accounts list in a report.
> Currently, all the accounts to be included when the report is run must
> exist at the time the report is defined, as the definition explicitly
> lists each account.  My proposal was that in defining a report the user
> should be able to mark an account so that when the report is run that
> account and all its children *existing when the report is run* (but not
> necessarily when it was defined) are included in the report.  This would
> imply that only a sparse list of accounts need be included in the report
> definition;  at report run-time the list of accounts *actually* existant
> would be compared with that sparse list and its flags, and the actual
> selection of accounts to include in the report would be made then, at
> report run-time.

The reason for this is that at the time the query code was written there
was no 'root' account, so there was no way to say "any account under X".
Now that we have root accounts we could very well do this.  Just a SMOP
to define a new QOF Query operation for Account GUID matching.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available


More information about the gnucash-user mailing list