<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Tinsology &#187; Databases</title> <atom:link href="http://tinsology.net/category/databases/feed/" rel="self" type="application/rss+xml" /><link>http://tinsology.net</link> <description>Searching for the Right Questions</description> <lastBuildDate>Wed, 25 Jan 2012 16:57:44 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>NoSQL</title><link>http://tinsology.net/2011/01/nosql/</link> <comments>http://tinsology.net/2011/01/nosql/#comments</comments> <pubDate>Thu, 20 Jan 2011 00:13:22 +0000</pubDate> <dc:creator>Tinsley</dc:creator> <category><![CDATA[Databases]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[neo4j]]></category> <category><![CDATA[NoSQL]]></category> <guid
isPermaLink="false">http://tinsology.net/?p=1349</guid> <description><![CDATA[Recently I've been working with a non-relational, graph DBMS called <a
href="http://neo4j.org/">Neo4j</a>. I've really only scratched the surface and it might just be a the temporary euphoria of working with something so new, but it feels liberating to be able to approach problems in a new way. It might also be that for the first time in a long time I'm working in Java. At this point I've written far <a
href="http://tinsology.net/2011/01/nosql/">Continue reading <span
class="meta-nav">&#8594;</span></a>]]></description> <wfw:commentRss>http://tinsology.net/2011/01/nosql/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Metadata</title><link>http://tinsology.net/2009/07/metadata/</link> <comments>http://tinsology.net/2009/07/metadata/#comments</comments> <pubDate>Thu, 02 Jul 2009 05:04:26 +0000</pubDate> <dc:creator>Tinsley</dc:creator> <category><![CDATA[Databases]]></category> <category><![CDATA[data]]></category> <category><![CDATA[meta]]></category> <category><![CDATA[metadata]]></category> <guid
isPermaLink="false">http://tinsology.net/?p=794</guid> <description><![CDATA[Throughout the life of a database there may come times when it needs to be updated to incorporate changes or new features. This may involve adding new attributes to existing entities; adding new columns to tables. The problem with this is that in a populated database, modifying the database schema can be very expensive with regard to performance. This is not something you want to do frequently on a live <a
href="http://tinsology.net/2009/07/metadata/">Continue reading <span
class="meta-nav">&#8594;</span></a>]]></description> <wfw:commentRss>http://tinsology.net/2009/07/metadata/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Creating a Secure Login System the Right Way</title><link>http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/</link> <comments>http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/#comments</comments> <pubDate>Tue, 30 Jun 2009 06:03:13 +0000</pubDate> <dc:creator>Tinsley</dc:creator> <category><![CDATA[Databases]]></category> <category><![CDATA[PHP]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[hash]]></category> <category><![CDATA[login]]></category> <category><![CDATA[passwords]]></category> <category><![CDATA[secure]]></category> <guid
isPermaLink="false">http://tinsology.net/?p=663</guid> <description><![CDATA[Making a custom login system is a common task for beginning PHP developers. Jumping right into it, however, may not be the best approach. There are several important aspects do building a login system that not only makes it work, but makes it safe. <a
href="http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/">Continue reading <span
class="meta-nav">&#8594;</span></a>]]></description> <wfw:commentRss>http://tinsology.net/2009/06/creating-a-secure-login-system-the-right-way/feed/</wfw:commentRss> <slash:comments>93</slash:comments> </item> <item><title>Validating User Input</title><link>http://tinsology.net/2009/04/validating-user-input/</link> <comments>http://tinsology.net/2009/04/validating-user-input/#comments</comments> <pubDate>Thu, 09 Apr 2009 17:51:14 +0000</pubDate> <dc:creator>Tinsley</dc:creator> <category><![CDATA[Databases]]></category> <category><![CDATA[PHP]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Validation]]></category> <guid
isPermaLink="false">http://tinsology.net/?p=370</guid> <description><![CDATA[Whenever you write an application that takes user input, you must assume users fall into two categories. Users who are incompetent, meaning that they are likely to provide incorrect input, and users that are attempting to exploit the system, meaning that they are trying to access, destroy, or manipulate information that they should not be able to. <a
href="http://tinsology.net/2009/04/validating-user-input/">Continue reading <span
class="meta-nav">&#8594;</span></a>]]></description> <wfw:commentRss>http://tinsology.net/2009/04/validating-user-input/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>PDO&#8230; Use It</title><link>http://tinsology.net/2009/04/pdo-use-it/</link> <comments>http://tinsology.net/2009/04/pdo-use-it/#comments</comments> <pubDate>Sun, 05 Apr 2009 03:17:25 +0000</pubDate> <dc:creator>Tinsley</dc:creator> <category><![CDATA[Databases]]></category> <category><![CDATA[PHP]]></category> <category><![CDATA[PDO]]></category> <guid
isPermaLink="false">http://tinsology.net/?p=170</guid> <description><![CDATA[The majority of PHP code I see, whether it be posted by a beginner on a forum, or built into a large application, seems to suggest that the current standard when accessing a database is to make use of whatever database specific commands PHP provides for your particular database (ie mysql_query, mssql_query, etc). Often times, calls to these function are coupled with various attempts to prevent sql injections (such as calls to mysql_real_escape_string). Altogether, however, to me it seems clumsy and insecure. <a
href="http://tinsology.net/2009/04/pdo-use-it/">Continue reading <span
class="meta-nav">&#8594;</span></a>]]></description> <wfw:commentRss>http://tinsology.net/2009/04/pdo-use-it/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Database Analysis Through Simulation</title><link>http://tinsology.net/2009/03/database-analysis-through-simulation/</link> <comments>http://tinsology.net/2009/03/database-analysis-through-simulation/#comments</comments> <pubDate>Tue, 10 Mar 2009 08:00:42 +0000</pubDate> <dc:creator>Tinsley</dc:creator> <category><![CDATA[Databases]]></category> <category><![CDATA[Programming]]></category> <category><![CDATA[Database]]></category> <category><![CDATA[Simulation]]></category> <guid
isPermaLink="false">http://tinsology.net/?p=165</guid> <description><![CDATA[Making adjustments to a database schema after it has gone into use is a daunting task. Whether it be because of efficiency issues or the incorporation of a new feature, this is a situation you should avoid at all costs. Often times, however, mistakes and inefficiencies are difficult to spot at implementation time. Only when your database has become populated, often by users who are counting on your applications to be reliable, do these things come to light. So what can you do? One solution is to run a simulation. <a
href="http://tinsology.net/2009/03/database-analysis-through-simulation/">Continue reading <span
class="meta-nav">&#8594;</span></a>]]></description> <wfw:commentRss>http://tinsology.net/2009/03/database-analysis-through-simulation/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
