Age | Commit message (Collapse) | Author | Files | Lines |
|
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
The following distfiles could not be fetched (some may be only fetched
conditionally):
./databases/cstore/distinfo D6.data.ros.gz
./databases/cstore/distinfo cstore0.2.tar.gz
./databases/cstore/distinfo data4.tar.gz
|
|
Upstream changes:
1.59 2021-02-22T13:25:52Z
- Added error detection for when a result set's callback doesn't return
an arrayref or arrayrefs
- Moved to GitLab for issue tracking
1.58 2020-11-02T13:34:48Z
- Added the ability for mock result sets to set custom attributes for
statement handles. Thanks to Erik Huelsmann for testing the new feature.
|
|
|
|
1.57 2020-09-18T06:57:48Z
- Fixed bug rt133358 t/016_mock_add_resultset_test.t fails (with older DBI)
1.56 2020-09-17T14:35:10Z
- The DBD::st module now supports the last_insert_id method
- Result sets with callbacks can now specify a last_insert_id
|
|
1.55 2019-12-30T14:20:00Z
- Fixed bug rt131264 t/033_table_info.t fails (with older DBI)
1.54 2019-12-23T12:44:22Z
- Added Bernhard Graf's 'Feature: one shot failure' merge request.
- Fixed description of the failure attribute of mock_add_resultset. It
no longer claims to support a hash ref (as it doesn't). Thanks to
Bernhard Graf for both the bug report and a merge request that fixes it.
- Fixed bug where it wasn't possible to replace a regular expression
mock resultset. Thanks to Bernhard Graf for both the bug report and
a merge request that fixes it.
- Fixed bug where the failure attribute wasn't working with regular
expression mock resultsets. Thanks to Bernhard Graf for both the bug
report and a merge request that fixes it.
1.53 2019-12-03T10:50:57Z
- Error handling in mock_add_resultset is no longer experimental
- Attribute Aliasing is no longer experimental
1.52 2019-10-28T11:35:41Z
- Added in callback feature for result sets so that their contents
can be more dynamic.
1.51 2019-10-23T11:43:51Z
- Fixed issue with using attribute aliases alongside a driver DSN
in the DBI->connect call
1.50 2019-10-22T19:37:26Z
- Added attribute aliases support for MariaDB
|
|
Upstream changes:
1.49 2019-09-12T12:59:51Z
- Fixing tests that fail on some old versions of Perl
1.48 2019-09-12T06:34:47Z
- Added execution_history feature to enable tracking of multiple
executes for prepared statements.
- Added support for $dbh->table_info calls
- Fixed bug rt91055 "insert IGNORE" doesn't raise last_insert_id
- Fixed bug rt82243 Bug with Regex in DBD::Mock::Session
1.47 2019-09-06T10:03:39Z
- Applied Max Carey's patch from rt86294 adding support for
nested keys to fetchall_hashref
- Added experimental Connection Callbacks feature
- Fixed build for Perl v5.8
1.46 2019-09-04T12:02:08Z
- Added git-repo url to meta-data
- Fixed bug rt70587 Spelling Mistake
- Added regex support to mock_add_resultset
|
|
Problems found with existing distfiles:
distfiles/D6.data.ros.gz
distfiles/cstore0.2.tar.gz
distfiles/data4.tar.gz
distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
|
|
Changes from previous:
1.43
- Segregated into different packages
- Removed code coverage from POD
- Fixed bug rt49537 Basic support for named parameters
- Fixed bug rt70421 Build.PL now contains Test::Exception
1.42
- Fixed bug rt66815 DBD::Mock::Session error clobbered
- Fixed bug rt69460 Info on META.yml is outdated
- Fixed bug rt69055 Spelling mistakes in POD
- RaiseError now works
|
|
* Changed incorrect verion number
Changes 1.40:
* Fixed bug rt44591 second preapre giving an error
* Fixed bug rt57981 warnings during clone
* Fixed bug rt63191 Synopsis errors
* Fixed bug rt66813 Google's group link in the POD
|
|
Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions
about your environment and ask the user to provide relevant connection
information. But if you need to test a framework that uses DBI,
particularly a framework that uses different types of persistence
schemes, then it may be more useful to simply verify what the
framework is trying to do -- ensure the right SQL is generated and
that the correct parameters are bound. DBD::Mock makes it easy to
just modify your configuration (presumably held outside your code)
and just use it instead of DBD::Foo (like DBD::Pg or DBD::mysql)
in your framework.
|