| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
- Updating package for p5 module SQL::Abstract from 1.51 to 1.53
- Setting license to gnu-gpl-v2
Upstream changes:
revision 1.53 2009-04-30 14:58 (UTC)
----------------------------
- make sure hash keys are sorted in all search sub-conditions
- switch installer from EU::MM to M::I
revision 1.52 2009-04-28 23:14 (UTC)
----------------------------
- allow -between to handle [\"", \""] and \["", @bind]
- allow order_by to handle -asc|desc => [qw/colA colB/] (artifact from DBIx::Class)
- more tests and clearing up of some corner cases
- t/10test.t does not run by default (developer only, too cpu intensive)
|
|
mainly Scalar::Util and List::Util
|
|
revision 1.51 2009-03-28 10:00 (UTC)
- fixed behavior of [-and => ... ] depending on the current
condition scope. This introduces backwards comp with 1.24
|
|
Approved by MAINTAINER.
Pkgsrc changes:
- Adjust dependencies
- Prevent installation of a temporary file included in the upstream
tarball
Upstream changes:
revision 1.50 2009-03-10 12:30 (UTC)
- fixed the problem with values() not behaving the same as the rest of the code (RT#43483)
- fixed interjecting arrayrefref into a where clause
- added value-only insert test with a literal SQL snippet
- cleanup and enhancement of t/03values.t
- better handling of borked SQL in tests
- deal properly with parentheses in is_same_sql_bind()
- fixed test subs (is_same_*) in SQL::Abstract::Test to return the correct test value
- do not version MANIFEST
Version 1.50 was a major internal refactoring of SQL::Abstract.
Great care has been taken to preserve the published behavior
documented in previous versions in the 1.* family; however,
some features that were previously undocumented, or behaved.
differently from the documentation, had to be changed in order
to clarify the semantics. Hence, client code that was relying
on some dark areas of SQL::Abstract v1.* might behave differently
in v1.50.
----------------------------
revision 1.49_04 2009-03-03
- add support for a [\%column_meta => value] bind value format
----------------------------
revision 1.49_03 2009-02-17
- clarify syntax of \['...', @bind] when used with a bindtype
of 'columns'
----------------------------
revision 1.49_02 2009-02-16
- added an AST-aware SQL::Abstract::Test library for sql syntax tests
- vastly expanded test coverage
- support for the { operator => \'...'|\['...', @bind] } syntax
allowing to embed arbitrary operators on the LHS
- fixed multiple regressions wrt DBIx::Class
----------------------------
revision 1.49_01 2009-02-11
- support for literal SQL through the [$sql, bind] syntax.
- added -nest1, -nest2 or -nest_1, -nest_2, ...
- optional support for array datatypes
- defensive programming : check arguments to functions/methods
- fixed bug with global logic of -and/-or (no side-effects any more)
- changed logic for distributing an op over arrayrefs
- fixed semantics of _bindtype on array args
- dropped the _anoncopy of the %where tree. No longer necessary.
- dropped the _modlogic function
- Make col => [] and col => {$op => [] } DTRT or die instead of generating
broken SQL. Added tests for this.
- Added { -desc => 'column' } order by support
- Tiny "$_"-related fix for { -desc => 'columns'} order by support
tests + docs
|
|
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
|
|
1.24 2008-07-09
- Ripped out all 1.23 changes
- Re-releasing 1.22 with DBIx::Class as maintainer
1.23 ????-??-??
1) Large patch by Laurent Dami to add all of the
following functionality:
- support for nested subqueries (see the doc for explanations)
- +/- prefixes in C<@order> columns, meaning 'ASC' or 'DESC'
- documentation :
- added an explanation about flexibility of argument types
(passing scalars instead of hashrefs/arrayrefs)
- added an example of a boolean column (through ref to empty
string)
- mentioned that select() can take an arrayref of tables
- added explanation of +/- prefixes in C<@order>
- WHERE section structured into subsections
- new subsection for nested queries
- suppressed the NOTES section about Morgan laws, because
subqueries provide support for compound logic statements.
These changes enable additional functionality in DBIx::DataModel
as well.
2) Patch by Robbie Bow to enable "quote_char" to take
an array ref. This fixes an issue to MS SQL Server,
since it requires that columns and tables be quoted with
surrounding [square brackets]
3) Patch by Norbert BUCHMULLER to enable the use of
the old-school-SQL operator for not-equal ('<>')
could be used for the 'IS NOT NULL' expression:
foo => { '<>' => undef }
This now properly generates:
foo IS NOT NULL
1.22 changes unknown (1.22 changelog empty)
|
|
|
|
can handle packages having no PLIST files.
|
|
Changes from 1.17:
revision 1.21
date: 2006/03/08 01:27:56; author: nwiger; state: Exp; lines: +5 -5
- bugfix for -1 setting off -and logic in modlogic()
----------------------------
revision 1.20
date: 2005/08/18 18:41:58; author: nwiger; state: Exp; lines: +104 -50
- added patch from Dan Kubb enabling quote_char and name_sep options
- added patch from Andy Grundman to enhance _anoncopy for deep refs
----------------------------
revision 1.19
date: 2005/04/29 18:20:30; author: nwiger; state: Exp; lines: +34 -20
added _anoncopy to prevent destroying original; updated docs
----------------------------
revision 1.18
date: 2005/03/07 20:14:12; author: nwiger; state: Exp; lines: +201 -65
added support for -and, -or, and -nest; see docs for details
|
|
of Perl files to deal with the perl-5.8.7 update that moved all
pkgsrc-installed Perl files into the "vendor" directories.
|
|
These paths are now relative to PERL5_PACKLIST_DIR, which currently
defaults to ${PERL5_SITEARCH}. There is no change to the binary
packages.
|
|
|
|
|
|
Description:
This module was inspired by the excellent the DBIx::Abstract manpage.
However, in using that module I found that what I really wanted to do
was generate SQL, but still retain complete control over my statement
handles and use the DBI interface. So, I set out to create an abstract
SQL generation module.
|
