Thanks to everyone for the ideas and suggestions. I want to get the
Activities and layouts completed for the last three areas (Payees,
Accounts and Categories) and then I will go back over this one bottle
neck. If all goes well and depending on how much time I get to work on
it over the weekend, I might get to it this weekend or next week.
On a side note I have two other questions:
1. Is it ok to discuss the development process of this here or should it
be moved elsewhere? I know this is not an "official" KMM application.
2. Is it ok to use icons/artwork from the original KMM in my app? I was
trying to model the user interface to KMM as close as possible given the
limitations of the platform I am working on.
Thanks again folks and I am excited to finally be making good progress
on this after attempting it so many times. :)
-Eric
On 08/12/2011 06:30 AM, Tony Bloomfield wrote:
On Thu, 11 Aug 2011 20:15:43 +0000 (GMT)
Colin Wright<cdwri...@gwi.net> wrote:
It looks like it could be really slow in a large data set. If this
is done a lot you'd want an index on kmmSplits(accountid, postDate)
(or kmmSplits(accountid, txType, postDate) if it does lots of
type-based searches and N is uncommon).
Unfortunately, 'N' is the most common. The alternative is 'S' which is
used only with template schedule transactions, not 'real' ones.
There is already an index on AccountId + txType; you can use
'Tools/Generate database SQL' in KMM to see the schema.
Please remember if you create indexes or views of your own not to name
them beginning with the three characters 'kmm' which are reserved for
'official' tables, etc.
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
