Important changes in trunk

Money Manager Ex Development related posts
(http://github.moneymanagerex.org/)
Vadim
MMEX Developer
Posts: 142
Joined: Mon Aug 03, 2009 7:35 am
Are you a spam bot?: No

Important changes in trunk

Post by Vadim »

Hi,
Some Important changes happened in trunk.

1.Sqlite3 sources replaced with the SQLite Amalgamation distribution (http://www.sqlite.org/amalgamation.html).

2.No more try-catch!!! Defines mmBEGINSQL_LITE_EXCEPTION, mmENDSQL_LITE_EXCEPTION have removed. You do not need to catch exceptions in every access to db.

3.Custom SQL Dialog removed from mmex as totally useless. It is useless for users because they do not know tables and relations in sqlite. It is useless for developers because it is too primitive and very uncomfortable. Anyone can use any suitable tools for sqlite found in inet which much more powerful.

4.mmex version promoted to 0.9.6.

Vadim
MMEX Developer
Posts: 142
Joined: Mon Aug 03, 2009 7:35 am
Are you a spam bot?: No

Re: Important changes in trunk

Post by Vadim »

I have found that some tests failed after updating of sqlite when you built mmex using MinGW. The VC++ mmex passes all tests.

madhan
Site Admin
Posts: 99
Joined: Sun Nov 30, 2008 8:06 pm

Re: Important changes in trunk

Post by madhan »

1.Sqlite3 sources replaced with the SQLite Amalgamation distribution (http://www.sqlite.org/amalgamation.html).
Please make sure this does not break Encryption support. Many people have DBs that are encrypted.
3.Custom SQL Dialog removed from mmex as totally useless. It is useless for users because they do not know tables and relations in sqlite. It is useless for developers because it is too primitive and very uncomfortable. Anyone can use any suitable tools for sqlite found in inet which much more powerful.
I agree with a lot of changes happening to the code base but I disagree here. It is not useless for users because they can just use Queries created by someone else. (See the forum for custom SQL). Using an additional tool is hard because someone has to download it and have it installed in the side and it is more work.

I would appreciate if existing functionality is not removed or atleast some kind of consensus is reached before doing so. My recommendation is not to remove this functionality and put it back.

Nikolay
MMEX Developer
Posts: 1287
Joined: Sat Dec 06, 2008 2:27 pm
Are you a spam bot?: No
Location: Sankt-Petersburg, Russia

Re: Important changes in trunk

Post by Nikolay »

Hi,

I believe that the Custom SQL report is a very cool feature, which is the hallmark of the program.

yampis
New MMEX User
Posts: 8
Joined: Sun Jul 19, 2009 8:41 pm
Are you a spam bot?: No

Re: Important changes in trunk

Post by yampis »

Hello!

Please, do not remove possibility to use Custom SQL directly in MMEX. At least for me, Custom SQL reports are more useful than default reports. If you want to remove these Custom SQL, then you have to revise and add much more reports to MMEX with possibility to customize parameters.

For example, you don't have any reports which groups expenses/incomes by category. Of course I can open detailed reports, where expenses/incomes are grouped by subcategories. But if I want to have quick look about my expenses/incomes my Custom SQL is much more useful that this detailed one...

Moreover, I'd like to have possibility to save my Custom SQL as "user" reports in MMEX for quick access...

elliswr
MMEX Developer
Posts: 102
Joined: Tue May 05, 2009 8:21 am
Are you a spam bot?: No
Location: Granbury, TX
Contact:

Re: Important changes in trunk

Post by elliswr »

I second the notion of being able to save the report and would like to add the ability to save it separate from MMEX (like a plugin). With this, users would be able to create their own reports and then post them so that others, who might find that particular report useful, could download and use. This be very beneficial for the MMEX community.

omalleypat
MMEX Developer
Posts: 112
Joined: Tue Jul 28, 2009 10:34 pm
Are you a spam bot?: No
Location: Atchison, KS

Re: Important changes in trunk

Post by omalleypat »

I think the Custom SQL should stay as well...

Vadim
MMEX Developer
Posts: 142
Joined: Mon Aug 03, 2009 7:35 am
Are you a spam bot?: No

Re: Important changes in trunk

Post by Vadim »

I removed custom SQL reports because it's very inconvenient in use. This functionality must be refactored. I think I will do this in next version after 0.9.5. Remember that svn trunk is for development, this is not release yet :-) 0.9.5 still has Custor SQL Report.

Vadim
MMEX Developer
Posts: 142
Joined: Mon Aug 03, 2009 7:35 am
Are you a spam bot?: No

Re: Important changes in trunk

Post by Vadim »

elliswr wrote:I second the notion of being able to save the report and would like to add the ability to save it separate from MMEX (like a plugin). With this, users would be able to create their own reports and then post them so that others, who might find that particular report useful, could download and use. This be very beneficial for the MMEX community.
I quite agree with elliswr.

Vadim
MMEX Developer
Posts: 142
Joined: Mon Aug 03, 2009 7:35 am
Are you a spam bot?: No

Re: Important changes in trunk

Post by Vadim »

Vadim wrote:I have found that some tests failed after updating of sqlite when you built mmex using MinGW. The VC++ mmex passes all tests.
All tests pass OK for trunk. Anyone can freely build mmex with MinGW.

Post Reply