Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I asked some programmers the same question once and the reply I got was that MySQL did not support sub-queries. Apparently PostgreSQL does which is what makes it better suited for databases with lots and lots of info that needs to be accessed quickly in different ways.
From what I've heard, MySQL and PGSQL both have their strengths and weaknesses when it comes to performance, but in addition to that, MySQL does not support several features (subqueries, transactions, e.t.c.) that PGSQL does...
I guess that's why PGSQL is ahead (at the time of posting).
Well, lets see, looking at the MySQL web site, and seeing things like "To avoid any any possible rollbacks, if you try to write a value that is out of bounds, MySQL will instead record the closest value and continue the transaction." I would say that makes it a very *poor* choice for Accounting. MySQL is great for weblogs and other services that require Lots of data access at highspeed with little regard to integrity.
P.S. I took that quote from memory.. It's probably not exactly the same wording as MySQL. (Chances are, it's not even close), but the idea is the same. Otherwise, someone please correct me.
You dont really need relationships, because your supposed to design good PHP code.
However, if you need an accountancy database, then MySQL does provide support for transactions and other features in the form of Inno DB tables and another form of table (cant remember the name). You have to get the MySQL Max version for these.