<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr - brownrl</title>
<link>http://snipplr.com/users/brownrl/tags/query</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Mon, 20 May 2013 12:49:24 GMT</pubDate>
<item>
<title>(JavaScript) Get Query String Args  Javascript</title>
<link>http://snipplr.com/view/59019/get-query-string-args--javascript/</link>
<description><![CDATA[ <p>This will get the arguments on the query string and put them into a handy array.</p> ]]></description>
<pubDate>Fri, 23 Sep 2011 17:33:12 GMT</pubDate>
<guid>http://snipplr.com/view/59019/get-query-string-args--javascript/</guid>
</item>
<item>
<title>(PHP) PHP dbquery</title>
<link>http://snipplr.com/view/16259/php-dbquery/</link>
<description><![CDATA[ <p>Here is a wrapper for making database queries. It doesn't matter who the F!@k you think you are you should always wrap querying the database in your own function.

WHY?

Because when you take your application to a new server, you won't have to change all the calls to mysql_query() to pg_sql_query() or $db->query() or what ever you are now using.

!!!Plus!!!

When you query fails you can handle that in a very nice way with a proper error screen and maybe send an email to your self.</p> ]]></description>
<pubDate>Wed, 24 Jun 2009 07:23:18 GMT</pubDate>
<guid>http://snipplr.com/view/16259/php-dbquery/</guid>
</item>
</channel>
</rss>