Hi Adam,
it was nice to speak with you.
I am waiting the change in the plan for issue 1513 as we agreed. As soon
you have changed the plan I will do again an estimation of the job.
It seems likely that this feature will be included in Mifos 1.2 or later:
what do you think?
To be remarked:
1. The Unit Test running on MyFly and not directly on MySQL can hide
problems:
1. There are cases in which the Unit Test is failing, but
functionally Mifos is working (as the one I experimented: the test failed
jus as I changed to lower case some table names. The workaround is
apparently to do the changes also and at the same time in the relate hbml
files. Due to the relationship between tables (think at LOOKUP tables for
example) what you propose is not 100% suitable.
1. 2. The job that has been done until now following your original plan
is now not anymore usable
1.3 The delivery must be rescheduled (I propose a complete delivery with
Mifos 1.2, with some intermediate delivery where it is possible
2. There could be cases where the Unit Test is successfully executed, but
Mifos is not working.
This want be a contribution also to the discussion "Downgrade/Upgrade what
for.."
Waiting your new plan, I will reassign the IT1513 to the Triagle for a
decision on my proposal to move this patch (global patch) to Mifos 1.2
Best Regards
Roberto
Musso/Ireland/Con
tr/[EMAIL PROTECTED]
To
Sent by: Adam Monsen <[EMAIL PROTECTED]>
mifos-developer-b cc
[EMAIL PROTECTED] Massimiliano
ceforge.net Parlione/Ireland/[EMAIL PROTECTED],
Mifos
Developer Mailing List
<[EMAIL PROTECTED]
03/05/2008 03:42 net>
PM Subject
[Mifos-developer] Test on
lower_case_table_names=1
Please respond to
Developer
<mifos-developer@
lists.sourceforge
.net>
Hi Adam,
I started the test on Windows and I have the following behavior that I
cannot explain and maybe you can do as you know the Mifos Unit test very
well.
Just putting the LOGMESSAGES name to logmessages in latest_schema.sql and
running the Unit Test I got the following error:
run_test:
[echo] Using database: test
[junit] Running org.mifos.application.Applic
[junit] );
[junit]
[junit] CREATE TABLE [logmessages](
[junit] LOG_ID INTEGER A...> but was:<...D
[junit] );
[junit]
[junit] CREATE TABLE [LOGMESSAGES](
[junit] LOG_ID INTEGER A...>)
[junit] command was:
[junit] DROP TABLE IF EXISTS LOGMESSAGES)
and the ant build file.
I tried with lower_case_table_names=1 and also the default for windows, but
still the same error.
The application seems working properly making the build avoiding Unit Test.
Have you any explanation?
Best
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
