Changes:
1.926 Wed Jan 11 15:48:11 UTC 2012
* Fix auto-reconnect when the server is dead or a
client timeout.
See https://github.com/melo/perl-redis/issues/1#issuecomment-3444989
1.925 Tue Jan 10 16:02:04 UTC 2012
* Implemented auto-reconnect
* Add support for UNIX domain sockets
* Make REDIS_SERVER work with both TCP and UNIX domain sockets
* Make the test suite workaround a missing redis-server binary
* Assorted small bug fixes
* Improve documentation
Changes:
0.11
- RT#41721 is completely fixed. (sorry, I updated only Makefile.PL and forgot to update META.yml)
- remove SUPPORT OPERATING SYSTEM in POD because description is too old.
- fix typo in POD (reported in RT#63121: Misprint in documentation)
0.10
- add missing dependency for Digest::SHA1 (reported in RT#41721)
- fix RT#36646
Changes:
2011-08-15 Patrick Galbraith <patg at patg dot net> (4.020)
* Numerous (!! Thank you!!) fixes for prepared statements: Masahiro Chiba <nihen at megabbs
dot com>
- Chop blanks fixed
- UTF8 improvements
- fixed memory allocation for BLOBs
- auto-reconnect
* Fix in leak test, which failed sometime due to first assignment $prev_size over
paging (Masahiro Chiba)
* Catalog test allows use of schemas other than 'test' (Masahiro Chiba)
* Documentation fix for auto_reconnect (Karen Etheridge <ether at cpan dot
org>)
* Win32 and general installation fixes (Alexandr Ciornii, http://chorny.net)
Changes:
0.797 (11.21.2011) - John Siracusa <siracusa@gmail.com>
* Fixed a bug that prevented explicitly disabling/enabling column
triggers from working (RT 72592)
Changes:
1.09 Mon 24 Oct 2011
- Spelling fix (gregoa herrmann)
- Updating to Module::Install 1.04
1.08 Wed 12 Oct 2011
- Adds support support for class based timelines
- Removed ORLite::Migrate::Perl as complex cases can now use the
class based timelines.
Changes:
1.51 Fri 25 Nov 2011
- Module::Install::DSL updated to 1.04
- Automatically load overlay classes if there exist. That is, where a
Foo/TableName.pm module exists in addition to the automatically
generated Foo::TableName class.
Changes:
0.74 2012-01-25
- Documentation:
* Re-release of 0.73, now with a proper changelog
0.73 2012-01-25
- Fixes:
* Allow prefetching of only a subset of the other table's columns (Alex Vandiver)
* Avoid a compilation failure on blead caused by incorrect precedence (Thomas Sibley)
Changes:
1.826 25 Jan 2012
* t/db-btree.t - fix use of "length @array"
[RT ##74336]
1.825 24 Jan 2012
* t/db-btree.t - fix use of "length @array"
[RT ##74336]
Changes:
0.08196 2011-11-29 05:35 (UTC)
* Fixes
- Fix tests for DBD::SQLite >= 1.34.
- Fix test failures with DBICTEST_SQLITE_USE_FILE set
- Fix the find() condition heuristics being invoked even when the
call defaults to 'primary' (i.e. when invoked with bare values)
- Throw much clearer error on incorrect inflation spec
- Fix incorrect storage behavior when first call on a fresh schema
is with_deferred_fk_checks
- Fix incorrect dependency on Test::Simple/Builder (RT#72282)
- Fix uninitialized warning in ::Storage::Sybase::ASE
- Improve/cache DBD-specific datatype bind checks (also solves a
nasty memleak with version.pm on multiple ->VERSION invocations)
- The internal carp module now correctly skips CAG frames when
reporting a callsite
- Fix test failures on perl < 5.8.7 and new Package::Stash::XS
- Fix TxnScopeGuard not behaving correctly when $@ is set at the
time of $guard instantiation
- Fix the join/prefetch resolver when dealing with ''/undef/()
relation specifications
* Misc
- No longer depend on Variable::Magic now that a pure-perl
namespace::clean is available
- Drop Oracle's Math::BigInt req down to 1.80 - no fixes concerning
us were made since
Changes:
1.35 Tue 29 Nov 2011
- Updated to SQLite 3.7.9 (ISHIGAKI)
- One small potential break case if you are using FTS4 and ^
1.34_03 Tue 1 Nov 2011
- Adding an explicit dynamic_config => 1 (ADAMK)
- bind_param SQL_INTEGER error now actually dies with RaiseError.
(ISHIGAKI)
1.34_02 Fri 21 Oct 2011
*** CHANGES THAT MAY POSSIBLY BREAK YOUR OLD APPLICATIONS ***
- Resolved#67581: bind_param SQL_INTEGER numifies value;
Now DBD::SQLite croaks if you explicitly specify datatype
(with bind_param) and datatype mismatch happens (ISHIGAKI)
- Datatype set in the bind_param(_array) becomes sticky now
(as per DBI spec). This potentially affects code depending on
current undocumented and broken behavior. (Yuriy Kaminskiy)
- Resolved#71311: binding output columns as SQL_BLOB returns
nothing (ISHIGAKI)
- Bsymbolic flag was not portable enough and was not silently
ignored under MacOSX. Needs to check harder to see if the
linker supports the option. (ISHIGAKI)
- Fixed binding named parameters. (Yuriy Kaminskiy)
- Moved check for bind_ph/is_inout so it always error-out.
(Yuriy Kaminskiy)
- Don't set imp_sth->stmt to NULL on error path (Yuriy Kaminskiy)
- Explained an issue of rollback with unfinished statements.
(ISHIGAKI)
1.34_01 Thu 22 Sep 2011
- Updated to SQLite 3.7.8 (ISHIGAKI)
- Made util/getsqlite.pl work properly for SQLite 3.7.5+ (ISHIGAKI)
- Cookbook: don't use globals (Yuriy Kaminskiy)
- Resolved#70135 and hopefully other mod_perl/CentOS issues like
#63873 and #47983, with a patch by MDOOTSON++ (ISHIGAKI)
While here, let to register egg-info.
What's new in psycopg 2.4.4
---------------------------
- 'register_composite()' also works with the types implicitly defined
after a table row, not only with the ones created by 'CREATE TYPE'.
- Values for the isolation level symbolic constants restored to what
they were before release 2.4.2 to avoid breaking apps using the
values instead of the constants.
- Named DictCursor/RealDictCursor honour itersize (ticket #80).
- Fixed rollback on error on Zope (ticket #73).
- Raise 'DatabaseError' instead of 'Error' with empty libpq errors,
consistently with other disconnection-related errors: regression
introduced in release 2.4.1 (ticket #82).
What's new in psycopg 2.4.3
---------------------------
- connect() supports all the keyword arguments supported by the
database
- Added 'new_array_type()' function for easy creation of array
typecasters.
- Added support for arrays of hstores and composite types (ticket #66).
- Fixed segfault in case of transaction started with connection lost
(and possibly other events).
- Fixed adaptation of Decimal type in sub-interpreters, such as in
certain mod_wsgi configurations (ticket #52).
- Rollback connections in transaction or in error before putting them
back into a pool. Also discard broken connections (ticket #62).
- Lazy import of the slow uuid module, thanks to Marko Kreen.
- Fixed NamedTupleCursor.executemany() (ticket #65).
- Fixed --static-libpq setup option (ticket #64).
- Fixed interaction between RealDictCursor and named cursors
(ticket #67).
- Dropped limit on the columns length in COPY operations (ticket #68).
- Fixed reference leak with arguments referenced more than once
in queries (ticket #81).
- Fixed typecasting of arrays containing consecutive backslashes.
- 'errorcodes' map updated to PostgreSQL 9.1.
* Support Berkeley DB 5.3.x.
* Drop support for Berkeley DB 4.2 and Python 2.3. Our reference
is Red Had Enterprise Linux 5, until march 2014.
* Support for "DBEnv->set_intermediate_dir()", available in
Berkeley DB 4.3-4.6. Patch by Garret Cooper.
* Support for "DB->set_dup_compare()". Original patches by
Nikita M. Kozlovsky and Ben Schmeckpeper.
* Fixed a testsuite compatibility problem with BDB 5.2.
* If we are running Solaris or derivatives, and 64bit python,
try to find the library under "/usr/local/Berkeley.*.*/64/".
* Solaris 10 Update 10 exposes a very old race condition in the replication
master election tests. Some details in
https://forums.oracle.com/forums/thread.jspa?messageID=9902860 .
Workaround proposed in a private email from Paula Bingham (Oracle),
in 20110929.
* When doing the full matrix test for a release, stop the verification
if any test failed.
* Added support for verifying named in-memory dbs.
* Added an integer key comparison function to improve performance through the
SQL API.
* Support build on the platforms where pthread_t is a struct.
* Added an API call so the user can specify the size of the region in a heap db.
* Improved Replication Manager's ability to recover from the (perhaps rare)
phenomenon of two sites trying to connect to each other simultaneously, which
used to result in loss of both connections, requiring a retry after the
CONNECTION_RETRY timeout period.
* Enhanced the interface for copying databases for a hot backup. Added configure
support for --enable-atomicfileread.
* Enhaced the log reading routine to detect that a log file is missing rather
than returning that a zero length record was found.
* Added pragma bdbsql_shared_resources to set or report the maximum amount of
memory to be used by shared structures in the main environment region and
bdbsql_lock_tablesize to set or report the number of buckets in the lock
object hash table. These are advanced tuning features for applications with
large number of tables or needs to reduce locking on concurrent long running
transactions.
* Added set_metadata_dir() and get_metadata_dir() to enable storage of
persistent metadata files in a location other than the environment home
directory.
* Improved the error handling through the SQL API. Errors can be sent to a file
with the use of the BDBSQL_ERROR_FILE pragma.
* Database handles can now be configured to give exclusive access to the
database.
* XA transactions will now use transaction snapshots if the XA databases they
operate on were configured with DB_MULTIVERSION.
* Added additional stats fields into the C# API
* Added pragma bdbsql_single_process to keep the Berkeley DB environment
information on the heap instead of in shared memory. This option cannot be
used if the database is accessed from multiple processes.
* Improved the ability of DB->compact to move DB_HASH database pages to the
begining of the file.
* The default schema format number is changed from 1 to 4. This means that,
unless the PRAGMA legacy_file_format=ON statement is run, newly created
database files will be unreadable by version of SQLite prior to 3.3.0
(2006-01-10). It also means that the descending indices are enabled by
default.
* The sqlite3_pcache_methods structure and the SQLITE_CONFIG_PCACHE and
SQLITE_CONFIG_GETPCACHE configuration parameters are deprecated. They are
replaced by a new sqlite3_pcache_methods2 structure and SQLITE_CONFIG_PCACHE2
and SQLITE_CONFIG_GETPCACHE2 configuration parameters.
* Added the powersafe overwrite property to the VFS interface. Provide the
SQLITE_IOCAP_POWERSAFE_OVERWRITE I/O capability, the
SQLITE_POWERSAFE_OVERWRITE compile-time option, and the "psow=BOOLEAN" query
parameter for URI filenames.
* Added the sqlite3_db_release_memory() interface and the shrink_memory pragma.
* Added the sqlite3_db_filename() interface.
* Added the sqlite3_stmt_busy() interface.
* Added the sqlite3_uri_boolean() and sqlite3_uri_int64() interfaces.
* If the argument to PRAGMA cache_size is negative N, that means to use
approximately -1024*N bytes of memory for the page cache regardless of the
page size.
* Enhanced the default memory allocator to make use of _msize() on windows,
malloc_size() on Mac, and malloc_usable_size() on Linux.
* Enhanced the query planner to support index queries with range constraints on
the rowid.
* Enhanced the query planner flattening logic to allow UNION ALL compounds to
be promoted upwards to replace a simple wrapper SELECT even if the compounds
are joins.
* Enhanced the query planner so that the xfer optimization can be used with
INTEGER PRIMARY KEY ON CONFLICT as long as the destination table is initially
empty.
* Enhanced the windows VFS so that all system calls can be overridden using the
xSetSystemCall interface.
* Updated the "unix-dotfile" VFS to use locking directories with mkdir() and
rmdir() instead of locking files with open() and unlink().
* Enhancements to the test_quota.c extension to support stdio-like interfaces
with quotas.
* Change the unix VFS to be tolerant of read() system calls that return less
then the full number of requested bytes.
* Change both unix and windows VFSes to report a sector size of 4096 instead of
the old default of 512.
* In the TCL Interface, add the -uri option to the "sqlite3" TCL command used
for creating new database connection objects.
* Added the SQLITE_TESTCTRL_EXPLAIN_STMT test-control option with the
SQLITE_ENABLE_TREE_EXPLAIN compile-time option to enable the command-line
shell to display ASCII-art parse trees of SQL statements that it processes,
for debugging and analysis.
* Bug fix: Add an additional xSync when restarting a WAL in order to prevent an
exceedingly unlikely but theoretically possible database corruption following
power-loss.
* Bug fix: Change the VDBE so that all registers are initialized to Invalid
instead of NULL.
* Bug fix: Fix problems that can result from 32-bit integer overflow.
* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for
InnoDB tables from concurrent threads could cause a deadlock, particularly
with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks
caused by the same row being accessed by more than one transaction. Deadlocks
could still occur when multiple rows are inserted and updated simultaneously
by different transactions in inconsistent order; those types of deadlocks
require the standard error handling on the application side, of re-trying the
transaction.
* An incorrect InnoDB assertion could cause the server to halt. This issue only
affected debug builds. The assertion referenced the source file btr0pcur.ic
and the variable cursor->pos_state.
* The handle_segfault() signal-handler code in mysqld could itself crash due to
calling unsafe functions.
* ARCHIVE tables with NULL columns could cause server crashes or become corrupt
under concurrent load.
* Enabling myisam_use_mmap could cause the server to crash.
* Concurrent access to ARCHIVE tables could cause corruption.
* A new server option, --slow-start-timeout, controls the Windows service
control manager's service start timeout. The value is the maximum number of
milliseconds that the service control manager waits before trying to kill the
MySQL service during startup. The default value is 15000 (15 seconds). If the
MySQL service takes too long to start, you may need to increase this value.
A value of 0 means there is no timeout.
Bugs Fixed:
* Important Change: Replication: Setting an empty user in a CHANGE MASTER TO
statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER
unset causes the statement to fail with an error.
* Important Change: Replication: Moving the binary log file, relay log file, or
both files to a new location, then restarting the server with a new value for
--log-bin, --relay-log, or both, caused the server to abort on start. This
was because the entries in the index file overrode the new location. In
addition, paths were calculated relative to datadir (rather than to the
--log-bin or --relay-log values).
* InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL
version reports that the page size is incompatible with the older version,
rather than crashing or displaying a “corruption” error.
* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for
InnoDB tables from concurrent threads could cause a deadlock, particularly
with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks
caused by the same row being accessed by more than one transaction. Deadlocks
could still occur when multiple rows are inserted and updated simultaneously
by different transactions in inconsistent order; those types of deadlocks
require the standard error handling on the application side, of re-trying the
transaction.
* An incorrect InnoDB assertion could cause the server to halt. This issue only
affected debug builds. The assertion referenced the source file btr0pcur.ic
and the variable cursor->pos_state.
* Locale information for FORMAT() function instances was lost in view
definitions.
* The handle_segfault() signal-handler code in mysqld could itself crash due to
calling unsafe functions.
* Enabling myisam_use_mmap could cause the server to crash.
* Concurrent access to ARCHIVE tables could cause corruption.
is useful to disable it if OpenLDAP was linked with pkgsrc's OpenSSL, since
nss_ldap will pull the base system OpenSSL dependency through Kerberos
libraries, leading to crashes because of multiple incomaptible libcrypto
linked.
PostGIS 1.5.3
2011/06/25
- This is a bug fix release, addressing issues that have been
filed since the 1.5.2 release.
- Bug Fixes
- #1056, produce correct bboxes for arc geometries, fixes index errors
(Paul Ramsey)
- #1007, ST_IsValid crash - fix requires GEOS 3.3.0+ or 3.2.3+
(Sandro Santilli, reported by Birgit Laggner)
- #940, support for PostgreSQL 9.1 beta 1
(Regina Obe, Paul Ramsey, patch submitted by stl)
- #845, ST_Intersects precision error (Sandro Santilli, Nicklas Avén)
Reported by cdestigter
- #884, Unstable results with ST_Within, ST_Intersects (Chris Hodgson)
- #779, shp2pgsql -S option seems to fail on points (Jeff Adams)
- #666, ST_DumpPoints is not null safe (Regina Obe)
- #631, Update NZ projections for grid transformation support (jpalmer)
- #630, Peculiar Null treatment in arrays in ST_Collect (Chris Hodgson)
Reported by David Bitner
- #624, Memory leak in ST_GeogFromText (ryang, Paul Ramsey)
- #609, Bad source code in manual section 5.2 Java Clients
(simoc, Regina Obe)
- #604, shp2pgsql usage touchups (Mike Toews, Paul Ramsey)
- #573 ST_Union fails on a group of linestrings
Not a PostGIS bug, fixed in GEOS 3.3.0
- #457 ST_CollectionExtract returns non-requested type
(Nicklas Avén, Paul Ramsey)
- #441 ST_AsGeoJson Bbox on GeometryCollection error (Olivier Courtin)
- #411 Ability to backup invalid geometries (Sando Santilli)
Reported by Regione Toscana
- #409 ST_AsSVG - degraded (Olivier Courtin)
Reported by Sdikiy
- #373 Documentation syntax error in hard upgrade (Paul Ramsey)
Reported by psvensso
PostGIS 1.5.2
2010/09/27
- This is a bug fix release, addressing issues that have been
filed since the 1.5.1 release.
- Bug Fixes
- Loader: fix handling of empty (0-verticed) geometries in shapefiles.
(Sandro Santilli)
- #536, Geography ST_Intersects, ST_Covers, ST_CoveredBy and
Geometry ST_Equals not using spatial index (Regina Obe, Nicklas Avén)
- #573, Improvement to ST_Contains geography
- Loader: Add support for command-q shutdown in Mac GTK build (Paul Ramsey)
- #393, Loader: Add temporary patch for large DBF files
(Maxime Guillaud, Paul Ramsey)
- #507, Fix wrong OGC URN in GeoJSON and GML output (Olivier Courtin)
- spatial_ref_sys.sql Add datum conversion for projection SRID 3021
(Paul Ramsey)
- Geography - remove crash for case when all geographies are out of
the estimate (Paul Ramsey)
- #469, Fix for array_aggregation error (Greg Stark, Paul Ramsey)
- #532, Temporary geography tables showing up in other user sessions
(Paul Ramsey)
- #562, ST_Dwithin errors for large geographies (Paul Ramsey)
- #513, shape loading GUI tries to make spatial index when loading DBF only
mode (Paul Ramsey)
- #527, shape loading GUI should always append log messages
(Mark Cave-Ayland)
- #504 shp2pgsql should rename xmin/xmax fields (Sandro Santilli)
- #458 postgis_comments being installed in contrib instead of
version folder (Mark Cave-Ayland)
- #474 Analyzing a table with geography column crashes server
(Paul Ramsey)
- #581 LWGEOM-expand produces inconsistent results
(Mark Cave-Ayland)
- #471 DocBook dtd errors (Olivier Courtin)
- Fix further build issues against PostgreSQL 9.0
(Mark Cave-Ayland)
- #572 Password whitespace for Shape File to PostGIS
Import not supported (Mark Cave-Ayland)
- #603: shp2pgsql: "-w" produces invalid WKT for MULTI* objects.
(Mark Cave-Ayland)
- Enhancement
- #513 Add dbf filter to shp2pgsql-gui and allow uploading dbf only
(Paul Ramsey)
* Internationalization
This version of GDBM is fully internationalized. The following
localizations are available: Finnish, German, Japanese, Polish and Ukrainian.
* Support for close-on-exec flag in gdbm_open (see GDBM_CLOEXEC in the docs).
* Improve testgdbm command system
The testgdbm tool now supports multicharacter commands.
* Bugfixes
Postgresql upstream does not use libtool. pkgsrc used to change
postgresql to use libtool, and this package was written to use the
pkgsrc-added libtool support. pkgsrc no longer modifies postgresql to
use libtool, so postgis did not build.
In addition to backing out all the make-postgis-use-libtool packages,
this commit adds a patch to add rpath to the PGSQL_FE_LDFLAGS, which
upstream hand constructs from pg_config output.
PKGREVISION++, but no change in version or functionality (from the
previous state, which also didn't build) intended.
0.9.12
-----
* On windows, the default ldap library became wldap32;
* Fixed compile with ruby 1.9.2.
Thank to Hiroki Najima!
* Fixed many memory leaks;
* Added functions:
LDAP::Conn.open_uri(uri);
LDAP::explode_dn(dn, notypes);
LDAP::explode_rdn(rdn, notypes).
Thanks to Marek Veber and Antonio Terceiro!
* Fixed bug in ldap/ldif.rb (GH-6).
Thanks to bbense.
* Fixed LDAP::Mod data corruption.
Thanks to Aprotim Sanyal!
* Enable client certificate authentication for mozilla ldap 6.0 only.
Thanks to Yuri Arabadji!
- bug #3442028 [edit] Inline editing enum fields with null shows
no dropdown
- bug #3442004 [interface] DB suggestion not correct for user with
underscore
- bug #3438420 [core] Magic quotes removed in PHP 5.4
- bug #3398788 [session] No feedback when result is empty
(signon auth_type)
- bug #3384035 [display] Problems regarding ShowTooltipAliasTB
- bug #3306875 [edit] Can't rename a database that contains views
- bug #3452506 [edit] Unable to move tables with triggers
- bug #3449659 [navi] Fast filter broken with table tree
- bug #3448485 [GUI] Firefox favicon frameset regression
- [core] Better compatibility with mysql extension
- [security] Self-XSS on export options (export server/database/table),
see PMASA-2011-20
- [security] Self-XSS in setup (host parameter), see PMASA-2011-19
Changes:
* Support SpiderMonkey 1.8.5
* Add configurable maximum to the number of bytes returned by _log.
* Allow CommonJS modules to be an empty string.
* Bump minimum Erlang version to R13B02.
* Do not run deleted validate_doc_update functions.
* ETags for views include current sequence if include_docs=true.
* Fix bug where duplicates can appear in _changes feed.
* Fix bug where update handlers break after conflict resolution.
* Fix bug with _replicator where include "filter" could crash couch.
* Fix crashes when compacting large views.
* Fix file descriptor leak in _log
* Fix missing revisions in _changes?style=all_docs.
* Improve handling of compaction at max_dbs_open limit.
* JSONP responses now send "text/javascript" for Content-Type.
* Link to ICU 4.2 on Windows.
* Permit forward slashes in path to update functions.
* Reap couchjs processes that hit reduce_overflow error.
* Status code can be specified in update handlers.
* Support provides() in show functions.
* _view_cleanup when ddoc has no views now removes all index files.
* max_replication_retry_count now supports "infinity".
* Fix replication crash when source database has a document with empty ID.
* Fix deadlock when assigning couchjs processes to serve requests.
* Fixes to the document multipart PUT API.
* Fixes regarding file descriptor leaks for databases with views.
Adapt for db4 update post 4.5.
Now dies with segfault during build:
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::substr
[1] Abort trap (core dumped) ./cstoreqptest 0...
Depends on Ruby on Rails 3 and here is CHANGELOG although it would not
be complete one.
* (16 Jun 2008) Backwards Compatibility is overrated (big updates for rails 2.1)
* Use ActiveRecord 2.1's dirty attribute checking instead [Asa Calow]
* Remove last traces of #non_versioned_fields
* Remove AR::Base.find_version and AR::Base.find_versions, rely on AR association proxies and named_scope
* Remove #versions_count, rely on AR association counter caching.
* Remove #versioned_attributes, basically the same as AR::Base.versioned_columns
* (5 Oct 2006) Allow customization of #versions association options [Dan Peterson]
*0.5.1*
* (8 Aug 2006) Versioned models now belong to the unversioned model. @article_version.article.class => Article [Aslak Hellesoy]
*0.5* # do versions even matter for plugins?
* (21 Apr 2006) Added without_locking and without_revision methods.
Foo.without_revision do
@foo.update_attributes ...
end
*0.4*
* (28 March 2006) Rename non_versioned_fields to non_versioned_columns (old one is kept for compatibility).
* (28 March 2006) Made explicit documentation note that string column names are required for non_versioned_columns.
*0.3.1*
* (7 Jan 2006) explicitly set :foreign_key option for the versioned model's belongs_to assocation for STI [Caged]
* (7 Jan 2006) added tests to prove has_many :through joins work
*0.3*
* (2 Jan 2006) added ability to share a mixin with versioned class
* (2 Jan 2006) changed the dynamic version model to MyModel::Version
*0.2.4*
* (27 Nov 2005) added note about possible destructive behavior of if_changed? [Michael Schuerig]
Dm-rails provides the railtie that allows datamapper to hook into rails3 and
thus behave like a rails framework component. Just like activerecord does in
rails, dm-rails uses the railtie API to hook into rails. The two are actually
hooked into rails almost identically.
Creating new datamapper apps on rails3 from scratch is actually really easy.
The following will guide you through the process.
This package brings tagging to DataMapper. It is inspired by Acts As Taggable
On by Michael Bleigh, github's mbleigh. Props to him for the contextual
tagging based on Acts As Taggable on Steroids.
== Features and Problems
=== Features
* Contextual tagging using Model.has_tags_on (see below for usage)
* Traditional 'tags-only' tagging using Model.has_tags
=== Problems
* None known yet, but this is very alpha software. Sorry if it misbehaves.
Please send me a github message if you find a bug.
dm-sweatshop is a model factory for DataMapper. It makes it easy & painless
to crank out complex pseudo random models -- useful for tests and seed data.
Production Goals:
* Easy generation of random models with data that fits the application domain.
* Simple syntax for declaring and generating model patterns.
* Add context to model patterns, allowing grouping and
* Effortlessly generate or fill in associations for creating complex models
with few lines of code.
DataMapper plugin enabling <b>simple</b> versioning of models.
When a model is versioned, and updated, instead of the previous version being
lost in the mists of time, it is saved in a subsidiary table, so that it can
be restored later if needed.
Please Note! this gem behaves differently to how AR's :acts_as_versioned
works. There is currently no multi version storage possible.
DataMapper plugin enabling easy creation of tree structures from your DM models.
This requires a foreign key property for your model, which by default would be
called :parent_id.
DataMapper plugin that adds state machine functionality to your models.
== Why is this plugin useful?
Your DataMapper resource might benefit from a state machine if it:
* has different "modes" of operation
* has discrete behaviors
* especially if the behaviors are mutually exclusive
And you want a clean, high-level way of describing these modes / behaviors
and how the resource moves between them. This plugin allows you to
declaratively describe the states and transitions involved.
A DataMapper search plugin api to search for resources from one repository and
load from another.
Typically a full text search adapter that can only produce partial resources is
searched and the resulting resource collection is then loaded from your default
repository.
DataMapper plugin allowing the creation of nested sets from data models.
Provides all the same functionality as dm-is-tree, plus tons more! Read on.
== What is a nested set?
Nested set is a clever model for storing hierarchical data in a flat table.
Instead of (only) storing the id of the parent on each node, a nested set puts
all nodes in a clever structure (see Example below). That is what makes it
possible to get the all of the descendants (not only immediate children),
ancestors, or siblings, in one single query to the database.
The only downside to nested sets (compared to trees] is that the queries it
takes to know these things, and to move nodes around in the tree are rather
complex. That is what this plugin takes care of (+ lots of other neat stuff)!
Nested sets are a good choice for most kinds of ordered trees with more than
two levels of nesting. Very good for menus, categories, and threaded posts.
Drop ${PHP_BASE_VARS} from PKGVERSION by default.
It used to be required to support multiple php version.
But after PHP version based ${PHP_PKG_PREFIX} was introduced,
such trick is not required anymore.
In addition to this, such version name schme invokes unwanted version bump
when base php version is bumped, plus, such version scheme is hard to
use for DEPENDS pattern.
To avoid downgrading of package using such legacy version scheme,
PECL_LEGACY_VERSION_SCHEME is introduced.
If it is defined, current version scheme is still used for currently
supported PHP version (5 and 53), but instead of ${PHP_BASE_VARS},
current fixed PHP base version in pkgsrc is used to avoid unwanted version bump
from update of PHP base package.
With newer PHP (54, or so on), new version scheme will be used if
it is defined.
This trick will not be required and should be removed after php5 and php53 will
be gone away from pkgsrc.
This release is focused on bug fixes, performance improvements,
internal refactoring and Rails 3.1 compatibility. Please give it a try
and in case of any issues please report them on Github.
* #valid? is always called even if a resource is not dirty
* Issues with JRuby and unicode were fixed
* Massive internal clean-up towards future rewrite that will make validations
even more awesome
