diff options
author | sno <sno> | 2010-03-16 17:30:08 +0000 |
---|---|---|
committer | sno <sno> | 2010-03-16 17:30:08 +0000 |
commit | 10d6905997b96ebb2fca8af7311b7709357c276a (patch) | |
tree | 90c65d6f2db8c91cd5e28b204801c2079c846bdf /databases/p5-SQL-Statement/DESCR | |
parent | bf8d14cfb9b9b356556e40519e5dfe18cf8d84ee (diff) | |
download | pkgsrc-10d6905997b96ebb2fca8af7311b7709357c276a.tar.gz |
Updating databases/p5-SQL-Statement from 1.22 to 1.25
pkgsrc changes:
- Adjust dependencies (mark fullfilled by perl CORE)
Upstream changes:
Version 1.25, release March 15th, 2010
----------------------------------------------
[Bug fixes]
* Keep org_table_names with schema information to allow derived
table classes to handle as it seems reasonable there
* Separate columns with "\0" in multi-column aggregation to be able to
difference between ('1','1foo') and ('11','foo')
[Misc]
* More resources added to META.yml
Version 1.24, release March 15th, 2010
----------------------------------------------
[Misc]
* Ignore *.rej in MANIFEST.SKIP (fixes RT #52081 reported by
Lars Thegler)
[Bug fixes]
* Add missing import of _INSTANCE in SQL::Statement::Function::NumericEval
fixes RT #52356 - reported by Detlef Pilzecker)
* Fix wrongly discarded DISTINCT clause (RT#53186)
[Improvements]
* Fix parsing errors of plain numbers (RT#16931)
* Fix parsing errors of nested calculation / functions (RT#16931, RT#52356)
* Rewrite result calculation of aggregation functions (simplify code,
speed up)
* Upgrade Makefile.PL (patch from Alexandr Ciornii) to handle different
EU::MM versions and abilities properly
* Update documentation to show how 'column_defs' and SQL::Statement::Term
instances shall be used
* Introduce SQL::Dialect::Role providing ini-style data access to
SQL::Dialects (patch from Michael Schwern)
[Things that may break your code]
* SQL::Parser now didn't deliver a struct containing 'column_names',
'computed_columns' and 'set_functions' - it's combined into one member
'column_defs'.
* Minimum required perl version is now 5.8 - upcoming next version of DBI
requires perl 5.8, too - and I could simplify some code that's why
Version 1.23, release November 20th, 2009
----------------------------------------------
[Misc]
* Applied patch from Marc Espie which fixes several orthographic
errors in SQL::Statement::Syntax documentation.
* Added a fixed version of test reported via RT #34121
[Bug fixes]
* Fix an issue in UPDATE command which 'shift's the values from
the list of parameters which causes there're no more parameters
left after first row get's updated (Fixes RT #50788)
* Fix aggregate function handling of new code since 1.21_01
* Correct handling of DISTINCT in aggregate functions
[Improvements]
* Add support for tables/columns starting with '_' for CSV and AnyData,
which is usually forbidden by ANSI SQL
* Add support for inserting multiple lines with one statement
(fixes RT #31730)
* Handle ANSI 'IS NULL' and CVS/AnyData 'IS NULL' different
[Things that may break your code]
* row_value now expects up to two arguments
Diffstat (limited to 'databases/p5-SQL-Statement/DESCR')
-rw-r--r-- | databases/p5-SQL-Statement/DESCR | 21 |
1 files changed, 18 insertions, 3 deletions
diff --git a/databases/p5-SQL-Statement/DESCR b/databases/p5-SQL-Statement/DESCR index bf947832d67..48fceedd113 100644 --- a/databases/p5-SQL-Statement/DESCR +++ b/databases/p5-SQL-Statement/DESCR @@ -1,3 +1,18 @@ -The SQL::Statement module implements a small, abstract SQL engine. This -module is not usefull itself, but as a base class for deriving concrete -SQL engines. +The SQL::Statement module implements a pure Perl SQL parsing and execution +engine. While it by no means implements full ANSI standard, it does support +many features including column and table aliases, built-in and user-defined +functions, implicit and explicit joins, complexly nested search conditions, +and other features. + +SQL::Statement is a small embeddable Database Management System (DBMS), +this means that it provides all of the services of a simple DBMS except that +instead of a persistant storage mechanism, it has two things: +1) an in-memory storage mechanism that allows you to prepare, execute, and + fetch from SQL statements using temporary tables and +2) a set of software sockets where any author can plug in any storage + mechanism. + +There are three main uses for SQL::Statement. +1) to access and manipulate data in CSV, XML, and other formats +2) to build a DBD for a new data source +3) to parse and examine the structure of SQL statements. |