summaryrefslogtreecommitdiff
path: root/databases/ruby-sequel-core
AgeCommit message (Collapse)AuthorFilesLines
2008-05-01Add a build dependency on ruby-rspec since the Rakefiles in thejlam1-1/+2
distribution include spec/rake/spectask.
2008-05-01Update databases/ruby-sequel-core to 1.5.1. Changes from version 1.5.0jlam2-6/+6
include: * Have Dataset#graph give a nil value instead of a hash with all nil values if no matching rows exist in the graphed table. This changes how graph handles missing records in associated tables (which occur because graph defaults to LEFT OUTER joins by design).
2008-04-29Update databases/ruby-sequel-core to 1.5.0. Changes from version 1.4.0jlam3-15/+13
include: * SECURITY: Fix backslash escaping of strings * No longer depend on ParseTree, RubyInline, or ruby2ruby, but you still need them if you want to use the block filters * Paginating an already paginated/limited dataset now raises an error * Added support for arbitrary index types (including spatial indexes) * Allow joining of multiple datasets, by making the table alias different for each dataset joined * Add ability to create a graph of objects from a query, with the result split into corresponding tables * Set a timeout in the Sqlite adapter, default to 5 seconds * Quote column names in SQL generated for SQLite * Add support for PostgreSQL partial indexes * Support storing microseconds in postgres timestamp fields * Fix table joining in MySQL * Fix MySQL default values insert * Fix renaming columns on MySQL with type :varchar * Fix ODBC adapter improperly escaping date and timestamp values * Fix connecting to an MSSQL server via ODBC using domain user credentials
2008-04-13Update databases/ruby-sequel-core to 1.4.0. Changes from version 1.3jlam4-9/+14
include fixes to the MySQL and PostgreSQL adapters.
2008-04-04Initial import of ruby18-sequel-core-1.3 as databases/ruby-sequel-core.jlam4-0/+98
Sequel is a database access toolkit for Ruby. Sequel provides thread safety, connection pooling, and a concise DSL for constructing queries and table schemas. Sequel makes it easy to deal with multiple records without having to break your teeth on SQL.