As we have said many times, we like things simple both for the user as for the rest of developers. To simplify programming and improve the performance of siwapp, we added the use of triggers in the database. What does this mean? It means that when a figure changes, the database automatically updates the total bill calculations.
The problem is that in MySQL 5.0, although the user has full permissions on her database, she can not create or run triggers on its database. The triggers execute permission is global to the system and no database administrator would agree to grant it.
Therefore, the minimum version of MySQL where this functionality is feasible is MySQL 5.1.6. For technical information you can consult the MySQL documentation.
Please remember to check again the specifications of your web hosting to make sure you install siwapp correctly.
9 Comments
What’s the timeline for this release? My server is behind on MySQL updates and I’m asking my host when we’ll be up to the right version.
Unfortunately there is no expected completion date. We are developing the application while working on other projects for our clients. Therefore, the development time is variable and we can not commit to a specific date. In any case, you can see the roadmap here: http://dev.siwapp.org/projects/siwapp/roadmap
Hi Carlos,
I wanted to test the 0.3 release with server MySQL 5.1.6 but version 5.1.6 is not out now right ?
I can’t install it as debian package even in Backports and also not on windows, as no 5.1.6 package is available.
Where have you found your package ?
@gael I have this line on /etc/apt/sources.list
deb http://www.backports.org/debian lenny-backports main contrib non-free
and with that, you can install mysql v.5.1.41
With that version, everything goes right.
hello,
i personally think it is a very bad idea.
today i tried to install siwapp, i was really happy to find an invoice management application that uses symfony. i really like the flexibility of symfony. the flexibility which is also based on the database abstraction layer.
my system: debian/lenny.apache2.php5.postgres
could not connect to database…
mysql only?
you are kidding, aren’t you?
why use such a great framework as symfony, which offer flexibility with the database abstraction and then cut it back down to the unflexibility of direct mysql_connect calls.
with you decision to hack-in direct mysql_connect calls you broke the whole cool symfony thing for me.
with the step to add triggers you go just a way further on being unflexible.
the application don’t need triggers in database layer. it performs good. so we can use native symfony events, tasks or equal symfony native operations to get the same result.
i beg you to go two steps back and use only symfony native operations. straight use the database abstraction layer.
add the installer as “mysql” only installer but add manual how to setup siwapp for other database servers. or maybe you can add an installer which supports all databases which are supported by symfony
greets
julian
I wholeheartly agree with Julian. Such a requirement for the database engine and version makes Siwapp a pain to install on a shared hosting or other standard installation.
I guess it’s a call to rethink the choice you’ve made.
Thanks.
I must say that you are right in part. What happens is that since the first moment we have struggled against Doctrine ORM. MySQL always has provided the easiest solution (not just in theory but also in reality).
Every time we tried to step forward we clashed against a wall. That meant we had to take hard decisions. We would like the application will work on any system with any database manager.
We’re giving for free what we can based in our current knowledge. So this is an open source project, so anyone can review the code, providing solutions, and so on.
Contributions are accepted. I hope that you may apologize.
@Carlos, I understand your stand. It’s your project and mostly what you do serves your particular needs first hand.
And it’s all fine with choosing MySql for this project. My point is that requiring MySql 5.1.x is tough for those on shared hosting. Siwapp is perfect for many SMB, freelancers, individuals and non-profits. The majority of those use shared hosting and keeping up with requirement for the database is going to be hard.
You’ve mentioned that you had troubles with updating total bill calculations. Can you point to the mailing list post or ticket that describes the problem and stuggles you’ve experienced? It’s open source, yes, but noone can step in and do something unless the problem is widely acknowledged and understood.
@Rian, @julian and @Carlos, I invite you to participate on this subject on the developers group: http://groups.google.com/group/siwapp-dev/browse_thread/thread/509cde985b262cba