Comments on: New system requirements for 0.3 release http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/ Free online invoice system Thu, 09 Feb 2012 11:44:43 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Swiss Web Hosting http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-514 Swiss Web Hosting Sun, 20 Mar 2011 06:34:24 +0000 http://www.siwapp.org/blog/?p=88#comment-514 Too bad it isn't compatible with MySQL 5.0. But this is one great development for the performance of siwapp. Triggers are of great help in terms of database manipulation! Too bad it isn’t compatible with MySQL 5.0. But this is one great development for the performance of siwapp. Triggers are of great help in terms of database manipulation!

]]> By: Jillian Renolds http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-303 Jillian Renolds Tue, 22 Jun 2010 18:47:41 +0000 http://www.siwapp.org/blog/?p=88#comment-303 GREAT WORK! HURRY UP! IT IS NEARLY ONE YEAR LATER! :) GREAT WORK!

HURRY UP!

IT IS NEARLY ONE YEAR LATER!

:)

]]> By: kaio http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-302 kaio Tue, 25 May 2010 21:41:20 +0000 http://www.siwapp.org/blog/?p=88#comment-302 when it leaves siwapp 0.3? when it leaves siwapp 0.3?

]]> By: We Take Back. No More New System Requirements For 0.3 Release. – siwapp - Free online invoice system http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-283 We Take Back. No More New System Requirements For 0.3 Release. – siwapp - Free online invoice system Fri, 09 Apr 2010 09:36:06 +0000 http://www.siwapp.org/blog/?p=88#comment-283 [...] people suggested (http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/#comment-277) the use of triggers, and the MySQL 5.1.6 or newer as a requirement was a bad idea. Well, today [...] [...] people suggested (http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/#comment-277) the use of triggers, and the MySQL 5.1.6 or newer as a requirement was a bad idea. Well, today [...]

]]> By: Umang http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-282 Umang Sun, 04 Apr 2010 16:40:57 +0000 http://www.siwapp.org/blog/?p=88#comment-282 Hey Carlos I wish to use Indian Rupee as my currency in the software but unfortunately the invoices show up some error. I would like you to please get it resolved in the new edition. Kudos for such an amazingly created software!! Hey Carlos
I wish to use Indian Rupee as my currency in the software but unfortunately the invoices show up some error. I would like you to please get it resolved in the new edition.
Kudos for such an amazingly created software!!

]]> By: Enrique http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-281 Enrique Sat, 27 Feb 2010 10:12:41 +0000 http://www.siwapp.org/blog/?p=88#comment-281 @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 @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

]]> By: Rian http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-280 Rian Tue, 16 Feb 2010 14:52:09 +0000 http://www.siwapp.org/blog/?p=88#comment-280 @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. @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.

]]> By: Carlos Escribano http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-279 Carlos Escribano Tue, 16 Feb 2010 10:30:20 +0000 http://www.siwapp.org/blog/?p=88#comment-279 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. 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.

]]> By: Rian http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-278 Rian Sun, 14 Feb 2010 19:01:57 +0000 http://www.siwapp.org/blog/?p=88#comment-278 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 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.

]]> By: julian http://www.siwapp.org/blog/2009/12/new-system-requirements-for-0-3-release/comment-page-1/#comment-277 julian Sun, 14 Feb 2010 17:01:50 +0000 http://www.siwapp.org/blog/?p=88#comment-277 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 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

]]>