8
0

Accepting request 898663 from devel:languages:perl:autoupdate

- updated to 1.00023
   see /usr/share/doc/packages/perl-SQL-SplitStatement/Changes
  1.00023   2021-06-05 22:10:21 IDT
  1.00022   2021-06-05 21:53:11 IDT (TRIAL RELEASE)
     * support REPLACE as an INSERT alternative (gh #5)
     * allow { and } to pass through in PL/Perl functions (gh #2)
  1.00021   2021-06-04 15:21:30 IDT (TRIAL RELEASE)
     * fix POD issues
     * fix issues with options in bin/sql-split (breaking, but wasn't working anyways)

OBS-URL: https://build.opensuse.org/request/show/898663
OBS-URL: https://build.opensuse.org/package/show/devel:languages:perl/perl-SQL-SplitStatement?expand=0&rev=5
This commit is contained in:
Andrey Karepin
2021-06-09 19:00:33 +00:00
committed by Git OBS Bridge
parent fe8abcef07
commit d5afaf26b6
5 changed files with 81 additions and 34 deletions

View File

@@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f77c30f44d87158d82f654e9fa94d39a50fdf7859c5a7fbd5813274666210f2f
size 56780

View File

@@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1a748420cd2ad341c2524ef1185b76ef7172969f17a9e4bab6f4376f0de9f35e
size 63709

35
cpanspec.yml Normal file
View File

@@ -0,0 +1,35 @@
---
#description_paragraphs: 3
#description: |-
# override description from CPAN
#summary: override summary from CPAN
#no_testing: broken upstream
#sources:
# - source1
# - source2
#patches:
# foo.patch: -p1
# bar.patch:
# baz.patch: PATCH-FIX-OPENSUSE
#preamble: |-
# BuildRequires: gcc-c++
#post_prep: |-
# hunspell=`pkg-config --libs hunspell | sed -e 's,-l,,; s, *,,g'`
# sed -i -e "s,hunspell-X,$hunspell," t/00-prereq.t Makefile.PL
#post_build: |-
# rm unused.files
#post_install: |-
# sed on %{name}.files
#license: SUSE-NonFree
#skip_noarch: 1
#custom_build: |-
#./Build build flags=%{?_smp_mflags} --myflag
#custom_test: |-
#startserver && make test
#ignore_requires: Bizarre::Module
#skip_doc: regexp_to_skip_for_doc.*
#add_doc: files to add to docs
#misc: |-
#anything else to be added to spec file
#follows directly after %files section, so it can contain new blocks or also
#changes to %files section

View File

@@ -1,3 +1,17 @@
-------------------------------------------------------------------
Sun Jun 6 03:08:46 UTC 2021 - Tina Müller <timueller+perl@suse.de>
- updated to 1.00023
see /usr/share/doc/packages/perl-SQL-SplitStatement/Changes
1.00023 2021-06-05 22:10:21 IDT
1.00022 2021-06-05 21:53:11 IDT (TRIAL RELEASE)
* support REPLACE as an INSERT alternative (gh #5)
* allow { and } to pass through in PL/Perl functions (gh #2)
1.00021 2021-06-04 15:21:30 IDT (TRIAL RELEASE)
* fix POD issues
* fix issues with options in bin/sql-split (breaking, but wasn't working anyways)
------------------------------------------------------------------- -------------------------------------------------------------------
Tue Jan 27 19:57:01 UTC 2015 - coolo@suse.com Tue Jan 27 19:57:01 UTC 2015 - coolo@suse.com

View File

@@ -1,7 +1,7 @@
# #
# spec file for package perl-SQL-SplitStatement # spec file for package perl-SQL-SplitStatement
# #
# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany. # Copyright (c) 2021 SUSE LLC
# #
# All modifications and additions to the file contributed by third parties # All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed # remain the property of their copyright owners, unless otherwise agreed
@@ -12,39 +12,37 @@
# license that conforms to the Open Source Definition (Version 1.9) # license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative. # published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/ # Please submit bugfixes or comments via https://bugs.opensuse.org/
# #
Name: perl-SQL-SplitStatement
Version: 1.00020
Release: 0
%define cpan_name SQL-SplitStatement %define cpan_name SQL-SplitStatement
Name: perl-SQL-SplitStatement
Version: 1.00023
Release: 0
Summary: Split any SQL code into atomic statements Summary: Split any SQL code into atomic statements
License: Artistic-1.0 or GPL-1.0+ License: Artistic-1.0 OR GPL-1.0-or-later
Group: Development/Libraries/Perl URL: https://metacpan.org/release/%{cpan_name}
Url: http://search.cpan.org/dist/SQL-SplitStatement/ Source0: https://cpan.metacpan.org/authors/id/V/VE/VEESH/%{cpan_name}-%{version}.tar.gz
Source: http://www.cpan.org/authors/id/E/EM/EMAZEP/%{cpan_name}-%{version}.tar.gz Source1: cpanspec.yml
BuildArch: noarch BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: perl BuildRequires: perl
BuildRequires: perl-macros BuildRequires: perl-macros
BuildRequires: perl(Class::Accessor::Fast) BuildRequires: perl(Class::Accessor::Fast)
BuildRequires: perl(List::MoreUtils) BuildRequires: perl(List::MoreUtils)
BuildRequires: perl(Regexp::Common) BuildRequires: perl(Regexp::Common)
BuildRequires: perl(SQL::Tokenizer) >= 0.22 BuildRequires: perl(Test::Differences) >= 0.68
BuildRequires: perl(Test::Exception) >= 0.27 BuildRequires: perl(Test::Exception) >= 0.270000
BuildRequires: perl(Test::More) >= 0.7 BuildRequires: perl(Test::More) >= 0.7
Requires: perl(Class::Accessor::Fast) Requires: perl(Class::Accessor::Fast)
Requires: perl(List::MoreUtils) Requires: perl(List::MoreUtils)
Requires: perl(Regexp::Common) Requires: perl(Regexp::Common)
Requires: perl(SQL::Tokenizer) >= 0.22
%{perl_requires} %{perl_requires}
%description %description
This is a simple module which tries to split any SQL code, even including This is a simple module which tries to split any SQL code, even including
non-standard extensions (for the details see the the /SUPPORTED DBMSs non-standard extensions (for the details see the SUPPORTED DBMSs section
manpage section below), into the atomic statements it is composed of. below), into the atomic statements it is composed of.
The logic used to split the SQL code is more sophisticated than a raw The logic used to split the SQL code is more sophisticated than a raw
'split' on the ';' (semicolon) character: first, various different 'split' on the ';' (semicolon) character: first, various different
@@ -52,34 +50,34 @@ statement terminator _tokens_ are recognized (see below for the list), then
this module is able to correctly handle the presence of said tokens inside this module is able to correctly handle the presence of said tokens inside
identifiers, values, comments, 'BEGIN ... END' blocks (even nested), identifiers, values, comments, 'BEGIN ... END' blocks (even nested),
_dollar-quoted_ strings, MySQL custom 'DELIMITER's, procedural code etc., _dollar-quoted_ strings, MySQL custom 'DELIMITER's, procedural code etc.,
as (partially) exemplified in the the /SYNOPSIS manpage above. as (partially) exemplified in the SYNOPSIS above.
Consider however that this is by no means a validating parser (technically Consider however that this is by no means a validating parser (technically
speaking, it's just a _context-sensitive tokenizer_). It should rather be speaking, it's just a _context-sensitive tokenizer_). It should rather be
seen as an in-progress _heuristic_ approach, which will gradually improve seen as an in-progress _heuristic_ approach, which will gradually improve
as test cases will be reported. This also means that, except for the the as test cases will be reported. This also means that, except for the
/LIMITATIONS manpage detailed below, there is no known (to the author) SQL LIMITATIONS detailed below, there is no known (to the author) SQL code the
code the most current release of this module can't correctly split. most current release of this module can't correctly split.
The test suite bundled with the distribution (which now includes the The test suite bundled with the distribution (which now includes the
popular _Sakila_ and _Pagila_ sample db schemata, as detailed in the the popular _Sakila_ and _Pagila_ sample db schemata, as detailed in the
/SHOWCASE manpage section below) should give you an idea of the SHOWCASE section below) should give you an idea of the capabilities of this
capabilities of this module module
If your atomic statements are to be fed to a DBMS, you are encouraged to If your atomic statements are to be fed to a DBMS, you are encouraged to
use the DBIx::MultiStatementDo manpage instead, which uses this module and use DBIx::MultiStatementDo instead, which uses this module and also
also (optionally) offers automatic transactions support, so that you'll (optionally) offers automatic transactions support, so that you'll have the
have the _all-or-nothing_ behavior you would probably want. _all-or-nothing_ behavior you would probably want.
%prep %prep
%setup -q -n %{cpan_name}-%{version} %autosetup -n %{cpan_name}-%{version}
%build %build
%{__perl} Makefile.PL INSTALLDIRS=vendor perl Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags} %make_build
%check %check
%{__make} test make test
%install %install
%perl_make_install %perl_make_install
@@ -87,7 +85,7 @@ have the _all-or-nothing_ behavior you would probably want.
%perl_gen_filelist %perl_gen_filelist
%files -f %{name}.files %files -f %{name}.files
%defattr(-,root,root,755) %doc Changes README
%doc Changes LICENSE README %license LICENSE
%changelog %changelog