<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 08 Jul 2008 23:00:25 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Derick Rethans' Blog: British date format parsing]]></title>
      <guid>http://www.phpdeveloper.org/news/9734</guid>
      <link>http://www.phpdeveloper.org/news/9734</link>
      <description><![CDATA[<p>
<i>Derick Rethans</i> has <z href="http://derickrethans.nl/british_date_format_parsing.php">posted about a new function</a> he's whipped up for PHP's date/time functionality to handle the differences between US formatted dates and the British date formats - date_create_from_format.
</p>
<blockquote>
From PHP 5.3 the new date_create_from_format() function and the DateTime::createFromFormat() factory method are available. As first argument they accept the expected format, and as second argument the string to parse.
</blockquote>
<p>
He <a href="http://derickrethans.nl/british_date_format_parsing.php">includes two examples</a> - one showing it being used to parse a British date string and the other to show off the date_get_last_errors function that can be useful for debugging.
</p>]]></description>
      <pubDate>Mon, 03 Mar 2008 20:45:49 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Wez Furlong's Blog: Calling SQLBindParameter and avoiding a datetime overflow.]]></title>
      <guid>http://www.phpdeveloper.org/news/4371</guid>
      <link>http://www.phpdeveloper.org/news/4371</link>
      <description><![CDATA[<i>Wez Furlong</i> has <a href="http://netevil.org/node.php?nid=700">this post</a> today  with a look at a problem he had with dates and <a href="http://www.cs.fsu.edu/~engelen/soap.html">gSOAP</a>.
<p>
<quote>
<i>
I've spent a lot of time with ODBC recently, working on interfacing our PostalEngine product with SQL Server. One of the things that caused me a LOT of trouble is binding date/time values into our stored procedure calls. One of the reasons that it was hard work was lack of documentation-by-example.
<p>
When this [code] is run, the execute fails with SQLSTATE 22008, Date time overflow. Everything looks correct in the code, and most of the values we're passing are based on the description of the parameter provided by ODBC, so what's going on?
</i>
</quote>
<p>
After "several hours", he <a href="http://netevil.org/node.php?nid=700">figures it out</a>, the problem being a result of the precision field. He also includes an example of the "magic number" to put in their field to get things to parse correctly...]]></description>
      <pubDate>Fri, 25 Nov 2005 06:44:58 -0600</pubDate>
    </item>
  </channel>
</rss>
