StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There are two good options here:</p> <h2><strong>PHP</strong></h2> <p>PHP is a server side language, and if you design the frontend with some robust classes, you can reuse the classes for the command-line daemon. This allows you to have a more standardized application suite, which will be easier to modify in the future. PHP can access MySQL, and since you already know it, the learning curve will be minimal.</p> <h2><strong>Python</strong></h2> <p>Python is an excellent server side language for an application like this. It can talk to any SQL database with a standardized instruction set, called <a href="http://www.python.org/dev/peps/pep-0249/" rel="nofollow noreferrer">DB API 2.0</a>. This means taht if at any point you want to change from MySQL to PostgresSQL, you simple change:</p> <pre><code>import my_mysql_library as sql </code></pre> <p>to:</p> <pre><code>import my_postgres_library as sql </code></pre> <p>And your application won't need any other code changes. Python also contains many libraries that might come in handy, and if optimized correctly, will be faster than PHP.</p> <h2><strong>Conclusion</strong></h2> <p>Personally, I would use Python, for the following reasons:</p> <ul> <li>Learning Experience; Programming is always about learning. At any opportunity, use a language or tool you don't already know so that you can <em>learn</em> it.</li> <li>Language Preference; After programming in both PHP and Python, I can honestly say that there is no situation where I would prefer to use PHP over Python. Not one.</li> <li>Available Libraries; Python has a very robust community, and a lot of useful libraries and packages (such as <a href="http://numpy.scipy.org/" rel="nofollow noreferrer">NumPy</a>) that make things <em>much</em> easier for you.</li> </ul> <p>With both languages you could have them run intermittently via a <a href="http://en.wikipedia.org/wiki/Cron" rel="nofollow noreferrer">cron job</a>, or you could have them run as a <a href="http://en.wikipedia.org/wiki/Daemon_%28computer_software%29" rel="nofollow noreferrer">Daemon</a> (which is as easy as running the script(s) while piping your output to a black hole, such as <a href="http://en.wikipedia.org/wiki//dev/null" rel="nofollow noreferrer">/dev/null</a>) </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload