rdo 0.0.4 → 0.0.5

data/lib/rdo/version.rb

@@ -6,5 +6,5 @@
 ##
 
 module RDO
-  VERSION = "0.0.4"
+  VERSION = "0.0.5"
 end

data/rdo.gemspec

@@ -10,22 +10,28 @@ Gem::Specification.new do |gem|
 
   If you're building something in Ruby that needs access to a database, you may
   opt to use an ORM like ActiveRecord, DataMapper or Sequel. But if your needs
-  don't fit well with an ORM (maybe you're even writing an ORM?) then you'll
+  don't fit well with an ORM—maybe you're even writing an ORM—then you'll
   need some other way of talking to your database.
 
   RDO provides a common interface to a number of RDBMS backends, using a clean
   Ruby syntax, while supporting all the functionality you'd expect from a robust
   database connection library:
 
-  * __Consistent API__ to connect to various DBMS's
-  * __Type casting__ to Ruby types
-  * __Time zone handling__ (via the DBMS, not via some crazy time logic in Ruby)
-  * __Native bind values__ parameterization of queries, where supported by the DBMS
-  * __Buffered result sets__ (i.e. cursors, to avoid exhausting memory)
-  * Retrieve query info from executed commands (e.g. affected rows)
-  * __Access RETURNING values__ just like any read query
-  * __Native prepared statements__ where supported, emulated where not
-  * Results given using simple __core Ruby data types__
+  <ul>
+    <li><strong>Consistent API</strong> to connect to various DBMS's</li>
+    <li><strong>Type casting</strong> to Ruby types</li>
+    <li><strong>Time zone handling</strong> (via the DBMS, not via some crazy
+      time logic in Ruby)</li>
+    <li><strong>Native bind values</strong> parameterization of queries, where
+      supported by the DBMS</li>
+    <li><strong>Buffered result sets</strong> (i.e. cursors, to avoid
+      exhausting memory)</li>
+    <li>Retrieve query info from executed commands (e.g. affected rows)</li>
+    <li><strong>Access RETURNING values</strong> just like any read query</li>
+    <li><strong>Native prepared statements</strong> where supported, emulated
+      where not</li>
+    <li>Results given using simple <strong>core Ruby data types</strong></li>
+  </ul>
 
   == RDBMS Support
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rdo
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.0.5
   prerelease: 
 platform: ruby
 authors:
@@ -27,60 +27,27 @@ dependencies:
     - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
-description: ! '== Ruby Data Objects
-
-
-  If you''re building something in Ruby that needs access to a database, you may
-
-  opt to use an ORM like ActiveRecord, DataMapper or Sequel. But if your needs
-
-  don''t fit well with an ORM (maybe you''re even writing an ORM?) then you''ll
-
-  need some other way of talking to your database.
-
-
-  RDO provides a common interface to a number of RDBMS backends, using a clean
-
-  Ruby syntax, while supporting all the functionality you''d expect from a robust
-
-  database connection library:
-
-
-  * __Consistent API__ to connect to various DBMS''s
-
-  * __Type casting__ to Ruby types
-
-  * __Time zone handling__ (via the DBMS, not via some crazy time logic in Ruby)
-
-  * __Native bind values__ parameterization of queries, where supported by the DBMS
-
-  * __Buffered result sets__ (i.e. cursors, to avoid exhausting memory)
-
-  * Retrieve query info from executed commands (e.g. affected rows)
-
-  * __Access RETURNING values__ just like any read query
-
-  * __Native prepared statements__ where supported, emulated where not
-
-  * Results given using simple __core Ruby data types__
-
-
-  == RDBMS Support
-
-
-  Support for each RDBMS is provided in separate gems, so as to minimize the
-
-  installation requirements and to facilitate the maintenace of each driver. Many
-
-  gems are maintained by separate users who work more closely with those RDBMS''s.
-
-
-  Due to the nature of this gem, most of the nitty-gritty code is actually
-
-  written in C.
-
-
-  See the official README for full details.'
+description: ! "== Ruby Data Objects\n\nIf you're building something in Ruby that
+  needs access to a database, you may\nopt to use an ORM like ActiveRecord, DataMapper
+  or Sequel. But if your needs\ndon't fit well with an ORM—maybe you're even writing
+  an ORM—then you'll\nneed some other way of talking to your database.\n\nRDO provides
+  a common interface to a number of RDBMS backends, using a clean\nRuby syntax, while
+  supporting all the functionality you'd expect from a robust\ndatabase connection
+  library:\n\n<ul>\n  <li><strong>Consistent API</strong> to connect to various DBMS's</li>\n
+  \ <li><strong>Type casting</strong> to Ruby types</li>\n  <li><strong>Time zone
+  handling</strong> (via the DBMS, not via some crazy\n    time logic in Ruby)</li>\n
+  \ <li><strong>Native bind values</strong> parameterization of queries, where\n    supported
+  by the DBMS</li>\n  <li><strong>Buffered result sets</strong> (i.e. cursors, to
+  avoid\n    exhausting memory)</li>\n  <li>Retrieve query info from executed commands
+  (e.g. affected rows)</li>\n  <li><strong>Access RETURNING values</strong> just like
+  any read query</li>\n  <li><strong>Native prepared statements</strong> where supported,
+  emulated\n    where not</li>\n  <li>Results given using simple <strong>core Ruby
+  data types</strong></li>\n</ul>\n\n== RDBMS Support\n\nSupport for each RDBMS is
+  provided in separate gems, so as to minimize the\ninstallation requirements and
+  to facilitate the maintenace of each driver. Many\ngems are maintained by separate
+  users who work more closely with those RDBMS's.\n\nDue to the nature of this gem,
+  most of the nitty-gritty code is actually\nwritten in C.\n\nSee the official README
+  for full details."
 email:
 - chris@w3style.co.uk
 executables: []