| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Changes since 0.7.10:
- Compatibility for Python 2.4 is being dropped.
- The primaryjoin argument is no longer needed when constructing a
relationship() against a class that has multiple foreign key paths to the
target.
- Relationships against self-referential, composite foreign keys where a
column points to itself are now supported.
- Previously difficult custom join conditions, like those involving
functions and/or CASTing of types, will now function as expected in most
cases.
- New Class/Object Inspection System.
- A new enhancement to the aliased() construct has been added called
with_polymorphic() which allows any entity to be “aliased” into a
“polymorphic” version of itself, freely usable anywhere.
- The PropComparator.of_type() method can now be used to target any number
of target subtypes, by combining it with the new with_polymorphic()
function.
- Mapper and instance events can now be associated with an unmapped
superclass, where those events will be propagated to subclasses as those
subclasses are mapped. The propagate=True flag should be used.
- The registry of class names is now sensitive to the owning module and
package of a given class. The classes can be referred to via dotted name
in expressions.
- The “deferred reflection” feature allows the construction of declarative
mapped classes with only placeholder Table metadata, until a prepare()
step is called, given an Engine with which to reflect fully all tables
and establish actual mappings. The system supports overriding of columns,
single and joined inheritance, as well as distinct bases-per-engine.
- A new SQL registration system allows a mapped class to be accepted as a
FROM clause within the core.
- The new UPDATE..FROM mechanics work in query.update().
- Upon rollback(), only those objects that were made dirty since the last
flush will be expired, the rest of the Session remains intact.
- Caching Example now uses dogpile.cache.
- The new operator system in Core associates new and overridden operators
with types.
- SQL expressions can now be associated with types.
- The inspect() function introduced in New Class/Object Inspection System
also applies to the core.
- select() now has a method Select.correlate_except() which specifies
“correlate on all FROM clauses except those specified”.
- Support for Postgresql’s HSTORE type is now available as
postgresql.HSTORE. This type makes great usage of the new operator system
to provide a full range of operators for HSTORE types, including index
access, concatenation, and containment methods such as has_key(),
has_any(), and matrix().
- The postgresql.ARRAY type will accept an optional “dimension” argument,
pinning it to a fixed number of dimensions and greatly improving
efficiency when retrieving results.
- SQLite has no built-in DATE, TIME, or DATETIME types, and instead
provides some support for storage of date and time values either as
strings or integers.
- The “collate” keyword, long accepted by the MySQL dialect, is now
established on all String types and will render on any backend, including
when features such as MetaData.create_all() and cast() is used.
- Geared towards MySQL, a “prefix” can be rendered within any of these
constructs.
- The consideration of a “pending” object as an “orphan” has been made more
aggressive.
- The after_attach event fires after the item is associated with the
Session instead of before; before_attach added.
- Query now auto-correlates like a select() does.
- Correlation is now always context-specific.
- create_all() and drop_all() will now honor an empty list as such.
- Repaired the Event Targeting of InstrumentationEvents.
- No more magic coercion of “=” to IN when comparing to subquery in
MS-SQL.
- The Session.is_modified() method accepts an argument passive which
basically should not be necessary, the argument in all cases should be
the value True - when left at its default of False it would have the
effect of hitting the database, and often triggering autoflush which
would itself change the results. In 0.8 the passive argument will have no
effect, and unloaded attributes will never be checked for history since
by definition there can be no pending state change on an unloaded
attribute.
- Column.key is honored in the Select.c attribute of select() with
Select.apply_labels().
- A relationship() that is many-to-one or many-to-many and specifies
“cascade=’all, delete-orphan’”, which is an awkward but nonetheless
supported use case (with restrictions) will now raise an error if the
relationship does not specify the single_parent=True option.
- Adding the inspector argument to the column_reflect event.
- The MySQL dialect does two calls, one very expensive, to load all
possible collations from the database as well as information on casing,
the first time an Engine connects. Neither of these collections are used
for any SQLAlchemy functions, so these calls will be changed to no longer
be emitted automatically. Applications that might have relied on these
collections being present on engine.dialect will need to call upon
_detect_collations() and _detect_casing() directly.
- Inspector.get_primary_keys() is deprecated, use
Inspector.get_pk_constraint.
- Case-insensitive result row names will be disabled in most cases. It will
be available only optionally, by passing the flag `case_sensitive=False`
to `create_engine()`, but otherwise column names requested from the row
must match as far as casing.
- The sqlalchemy.orm.interfaces.InstrumentationManager class is moved to
sqlalchemy.ext.instrumentation.InstrumentationManager.
- SQLSoup is now moved into its own project and documented/released
separately; see https://bitbucket.org/zzzeek/sqlsoup.
- The older “mutable” system within the SQLAlchemy ORM has been removed.
- We had left in an alias sqlalchemy.exceptions to attempt to make it
slightly easier for some very old libraries that hadn’t yet been upgraded
to use sqlalchemy.exc. Some users are still being confused by it however
so in 0.8 we’re taking it out entirely to eliminate any of that confusion.
|
|
From the release announcement:
This is a bug fix release which includes the following fixes:
* Allow the dump of pg schemas [Guillaume Lelarge]]
* Prevent a crash on Windows when dropping a column or a constraint on
a table [Dhiraj Chawla]
* Ensure DDLScript will work with Slony 2.2+ which has a new SQL level
API [Neel Patel]
* Fix ordering of object types in the display options and add Event
Triggers which were missing [Dhiraj Chawla].
* Ensure the debugger can cope with functions that have an OUT
parameter as the first. [Ashesh Vashi]
* Fix the quoting of user mapping objects [Dinesh Kumar]
* Ensure that materialised views are available as targets for synonyms
[Neel Patel]
* Fix the query used to find tables in a Slony replication set [Neel Patel]
* Prevent a crash if a user starts an external process such as a
backup, and then immediately hits cancel [Neel Patel].
* Fix a memory leak in the Event Trigger code [Dinesh Kumar].
For more information or to download, please visit the website at
http://www.pgadmin.org/.
|
|
Guarantee transmission of all WAL files before replica failover
Prevent downcasing of non-ASCII identifiers
Fix several minor memory leaks
Correct overcommit behavior when using more than 24GB of work memory
Improve planner cost estimates for choosing generic plans
Fix estimates of NULL rows in boolean columns
Make UNION ALL and inheritance query plans recheck parameterized paths
Correct pg_dump bugs for foreign tables, views, and extensions
Prevent a parallel pg_restore failure on certain indexes
Make REINDEX revalidate constraints
Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
Prevent GiST index lookup crash
Fix several regular expression failures
Allow ALTER DEFAULT PRIVILEGES to work on all schemas
Loosen restrictions on keywords
Allow various spellings of infinity
Expand ability to compare rows to records and arrays
Prevent psql client crash on bad PSQLRC file
Add spinlock support for ARM64
|
|
Guarantee transmission of all WAL files before replica failover
Prevent downcasing of non-ASCII identifiers
Fix several minor memory leaks
Correct overcommit behavior when using more than 24GB of work memory
Improve planner cost estimates for choosing generic plans
Fix estimates of NULL rows in boolean columns
Make UNION ALL and inheritance query plans recheck parameterized paths
Correct pg_dump bugs for foreign tables, views, and extensions
Prevent a parallel pg_restore failure on certain indexes
Make REINDEX revalidate constraints
Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
Prevent GiST index lookup crash
Fix several regular expression failures
Allow ALTER DEFAULT PRIVILEGES to work on all schemas
Loosen restrictions on keywords
Allow various spellings of infinity
Expand ability to compare rows to records and arrays
Prevent psql client crash on bad PSQLRC file
Add spinlock support for ARM64
|
|
Update hstore extension with JSON functionality
Prevent memory leak when creating range indexes
Fix libpq SSL deadlock bug
|
|
|
|
|
|
The following bugs were fixed since the release of version 4.0.7:
- bug #3988 Rename view is not working
- bug #4041 Interaction between linkified fields and grid editing
- bug #3975 Table grouping isn't implemented properly
- bug #4060 Browser tries to remember wrong password when creating new user
- bug #4002 Edit Index on big table doesn't show "Loading" or any message
- bug #4098 Default table tab is ignored
- bug #4099 Server/library difference warning: setting is ignored
- bug #4100 table tree group strategy
- bug #4102 ALTER TABLE ORDER BY and InnoDB
- bug #4103 Tracking report: cannot delete a statement
- bug #3996 Drizzle navigation doesn't expand
- bug #4074 GIS column editor: point not displayed
- bug #4109 Drizzle tables in navigation are shown as views
- bug #4095 NUL symbols added to the end of database dump file
- bug #4105 More disappears in table Structure
- bug #3992 Multi-row edit doesn't clear values when checking NULL
|
|
|
|
|
|
|
|
However, redirect stderr to /dev/null to get rid of unnecessary warning
that triggered 1.4.
|
|
|
|
|
|
This moves to Gnome 3 environment.
|
|
shared-mime-info 1.2 (2013-09-30)
* Mime-type changes:
- Use IANA registered application/sql type for SQL
- Add test for text/x-python
- Added *.pyx as Pyrex/Cython variant of text/x-python
- Lower the priority of the *png glob on Apple PNGs
- Add magic for Kobo e-book reader
- Add another magic for EPub books
- Add missing globs and tests for OpenPGP files
- Add MIME types for raw disk images
- Add video/x-matroska-3d mime-type
- Use application/vnd.adobe.flash.movie for SWF
- Use application/vnd.nintendo.snes.rom for SNES ROMs, associate *.sfc with them
- Fix shebang matches for shell scripts
- Remove *.ogv as a glob for Theora videos as they might not be Theora
- Improve detection of Perl scripts
- Add more aliases for Photoshop images
- Add Microsoft Publisher mime-type
- Correct JPEG2000 definition
* Check for errors when saving files, and ensure that files
are saved to disk before carrying on.
* Don't use access() to check for writability
* Rename configure.in to configure.ac
|
|
|
|
generation of DLLs.
|
|
|
|
HSQLDB (HyperSQL DataBase) is the leading SQL relational database
engine written in Java. It offers a small, fast multithreaded and
transactional database engine with in-memory and disk-based tables
and supports embedded and server modes.
This package contains library file (hsqldb.jar) only, and it is
old and should be used only for LibreOffice package.
|
|
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write.
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping.
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages.
* Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution.
* The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag.
* For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash.
* For DIV expressions, assignment of the result to multiple variables could cause a server crash.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax.
* If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
|
|
* MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.6 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File.
* Important Change; Replication: START SLAVE UNTIL SQL_AFTER_GTIDS did not cause the slave to stop until the next GTID event was received following execution of the transaction having the indicated GTID, which could cause issues in the case when the next GTID event is delayed, or does not exist. Now the slave stops after completing the transaction with that GTID.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows.
* InnoDB: When logging the delete-marking of a record during online ALTER TABLE...ADD PRIMARY KEY, InnoDB writes the transaction ID to the log as it was before the deletion or delete-marking of the record. When doing this, InnoDB would overwrite the DB_TRX_ID field in the original table, which could result in locking issues.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: An assertion would be raised in fil_node_open_file due to a missing .ibd file. Instead of asserting, InnoDB should return false and the caller of fil_node_open_file should handle the return message.
* InnoDB: The assertion ut_ad(oldest_lsn <= cur_lsn) in file buf0flu.cc would fail because the current max LSN would be retrieved from the buffer pool before the oldest LSN.
* InnoDB: InnoDB memcached add and set operations would perform more slowly than SQL INSERT operations.
* InnoDB: The InnoDB memcached plugin could be initialized to insert into an InnoDB table with an INTEGER primary key.
More...
|
|
* MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.5 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write.
* InnoDB: A regression introduced with the fix for Bug 11762038 would cause InnoDB to raise an incorrect error message. The message stated that, “InnoDB cannot delete/update rows with cascading foreign key constraints that exceed max depth of 20”. The error message would occur when killing connections reading from InnoDB tables that did not have foreign key constraints.
* InnoDB: The documentation incorrectly stated that START TRANSACTION WITH CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT SNAPSHOT only works with REPEATABLE READ. All other isolation levels are ignored. The documentation has been revised and a warning is now generated whenever the WITH CONSISTENT SNAPSHOT clause is ignored.
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping.
more...
|
|
|
|
sqlparse is a non-validating SQL parser module for Python.
|
|
- bug #3993 Sorting in database overview with statistics doesn't work
- bug Handle the situation where PHP_SELF is not set
- bug #4080 Overwrite existing file not obeyed
- bug #3929 Database-specific privileges are not copied when cloning user
- bug #3997 Error handling in case MySQL extension is missing
- bug #4089 Moving Columns will alter column definition
- bug #4091 Insert ignore option does not work
- bug #4090 Downloading BLOB downloads page template
- bug #4092 Clicking on table name in view of information_schema redirects to wrong page
- bug #4079 Copy Table Add AUTO_INCREMENT value checkbox not working
- bug #4088 MySQL server version at index.php incorrect w/ controlhost
- bug #4001 Import error: Class 'ImportOds' not found
- bug #3986 Missing DROP VIEW button
Approved by Thomas Klausner.
|
|
|
|
|
|
The major changes since version 3.5.* are:
- HTML frames are gone.
- The navigation panel now presents a tree.
- Javascript now required
- Documentation has a new look.
- Many bug fixes and smaller new features
This update also fixes the security vulnerability reported in PMASA-2013-10.
Approved by Thomas Klausner.
|
|
No changelog, but at least, buildable with recent MySQL.
while here:
* removed OpenSSL related stuffs, no reason is found.
* set LICENSE=gnu-gpl-v2 (or later).
* drop needless definitions.
|
|
Exact changes aren't available. Please refer change log in github.
|
|
Exact changes aren't available. Please refer change log in github.
|
|
v0.22.0
- Add new composite API to resolve ambiguity between unpacking a composite and packing a composite with one element (issue #196, courtesy @kevinkehl)
- Breaking change: schema change methods no longer catch exceptions internally. They work the same as everything else.
v0.21.0
- Add 1.2 libs to gem
v0.19.0
- Fixed windows build by disabling native extensions (issue #188, courtesy @jacek99)
- Speed improvement to native composite column extension (issue #186, courtesy @muirmanders)
- Fix OrderedHash iterator return values (issue #185, courtesy @fester)
- Native support for dynamic composite decoding (issue #184, courtesy @muirmanders)
v0.18.0
- Cassandra 1.2 support (issue #175, courtesy @brainopia)
- drop_keyspace defaults to current keyspace (issue #176, courtesy @brianopia)
- Easier flush_batch interface (issue #182, courtesy @brianopia)
- Support for removing multiple columns (issue #183, courtesy @brianopia)
|
|
Bump PKGREVISION.
But this version is known that it is incompatible with 5.1 (and later?) API,
so maeked as BROKEN.
|
|
Bump PKGREVISION.
|
|
Bump PKGREVISION.
|
|
|
|
MySQL and InnoDB transaction/status monitor. Like 'top' for MySQL. Displays
queries, InnoDB transactions, lock waits, deadlocks, foreign key errors, open
tables, replication status, buffer information, row operations, logs, I/O
operations, load graph, and more. You can monitor many servers at once with
innotop.
|
|
|
|
hides strlen(), causing linker failure later.
|
|
== v0.16.0 [2013-07-22] Michael Granger <ged@FaerieMUD.org>
Bugfixes:
- Avoid warnings about uninitialized instance variables.
- Use a more standard method of adding library and include directories.
This fixes build on AIX (Github #7) and Solaris (#164).
- Cancel the running query, if a thread is about to be killed (e.g. by CTRL-C).
- Fix GVL issue with wait_for_notify/notifies and notice callbacks.
- Set proper encoding on the string returned by quote_ident, escape_literal
and escape_identifier (#163).
- Use nil as PG::Error#result in case of a NULL-result from libpq (#166).
- Recalculate the timeout of conn#wait_for_notify and conn#block in case
of socket events that require re-runs of select().
Documentation fixes:
- Fix non working example for PGresult#error_field.
Enhancements:
- Add unique exception classes for each PostgreSQL error type (#5).
- Return result of the block in conn#transaction instead of nil (#158).
- Allow 'rake compile' and 'rake gem' on non mercurial repos.
- Add support for PG_DIAG_*_NAME error fields of PostgreSQL-9.3 (#161).
|
|
Changes from 3.48.0 are too many to write here, please refer CHANGELOG
file.
|
|
|
|
pgAdmin III Changelog
=====================
Notes
-----
This is the pgAdmin III changelog. Items are marked with the initials of the
developer responsible for them, and the version of pgAdmin that the change
will first appear in. For convenience, changes during Beta and RC phases may
include an RCx or Bx suffix on the version number, but for simplicity these
will not normally be retained.
A name in square braces [Joe Bloggs] indicates that the change was written by
Joe. The initialed developer was responsible for reviewing the changes in these
cases.
Names shown as "per Joe Bloggs", indicate that Joe reported the problem and may
have provided help debugging it, but did not actually provide the change.
Key to developers
-----------------
- DP Dave Page
- AP Andreas Pflug
- JMP Jean-Michel Poure
- HS Hiroshi Saito
- AHP Adam H. Pendleton
- MP Marc Persuy
- DAP Darko Prenosil
- FGP Florian G. Pflug
- MH Magnus Hagander
- GL Guillaume Lelarge
- AV Ashesh Vashi
Changes
-------
Date Dev Ver Change details
---------- --- ------ --------------
2013-09-06 DP 1.18.1 Fix a memory leak in the Event Trigger code [Dinesh
Kumar].
2013-08-20 AV 1.18.0 Fix a layout bug in the graphical explain renderer that
could render nodes on top of each other.
2013-08-06 DP 1.18.0 Fix Slony's DDL Script support [Akshay Joshi].
2013-07-26 DP 1.18.0 Add support for Event Triggers in 9.3+ [Dinesh Kumar].
2013-07-22 DP 1.18.0 Avoid using a Help cache file that needs to be world
writeable, and ensure sed is happy when post-processing
helpfiles.
2013-07-22 DP 1.18.0 Fix the help path on the import dialogue and improve the
error handling [Akshay Joshi].
2013-07-22 DP 1.18.0 Fix path the the Search Objects help doc [Dhiraj Chawla].
2013-07-18 GL 1.18.0 Fix UTF-8 display for guru hints [Marek Cernocky].
2013-07-08 DP 1.18.0 Prevent a crash when creating a stored procedure in
PPAS [Dinesh Kumar].
2013-06-19 GL 1.18.0 Disable the Favourites menu items if there is no
favourites file path (per a comment from Michael Shapiro).
2013-06-18 GL 1.18.0 Make No the default button on the Truncate confirmation
dialog (per request from Humberto Cereser Ibanez).
2013-06-18 DP 1.18.0 Support Materialized Views [Neel Patel].
2013-06-07 DP 1.18.0 Avoid a possible crash on Linux when using the
"Script" options of the Query Tool [aditsu].
2013-05-26 DP 1.18.0 Fix comments on constraints [Thom Brown].
2013-05-26 DP 1.18.0 Fix schema prefixes in cast definitions in the browser.
2013-05-26 DP 1.18.0 Treat sequences as first class objects in the Grant
Wizard. Support USAGE and remove obsolete RULE
permissions [Dhiraj Chawla].
2013-05-26 DP 1.18.0 Set the default backup type to "Custom".
2013-05-21 DP 1.18.0 Improve the copy handling on the Edit Grid so that
it works more consistently and predictably.
2013-05-20 DP 1.18.0 Fix comments on columns.
2013-05-20 DP 1.18.0 Remove the "Apply" buttons from the function, view
package and external table dialogues. Their use is
discouraged, and the code is fragile, complex and
very buggy.
2013-05-20 DP 1.18.0 Fix a crash that could occur if the browser fails to
detect that an object has been changed by another
session.
2013-05-17 DP 1.18.0 Change the default SQL box font to a slightly smaller
size on GTK based platforms.
2013-05-17 DP 1.18.0 Don't prompt the user for a password if they're using
a client certificate.
2013-05-17 DP 1.18.0 Ensure global backups use the mintenance database to
avoid access issue with postgres or template1.
2013-05-17 DP 1.18.0 Fix SSL certificate authentication.
2013-05-08 DP 1.18.0 Fix renaming and schema changes for stored procedures
in PPAS [Dinesh Kumar].
2013-05-02 DP 1.18.0 Add SSH tunnelling support to allow connections to be
made to hosts via an SSH server [Akshay Joshi].
2013-05-02 DP 1.18.0 Display the index validity in the properties list for
indexes and index-based constraints [Gabrielle Roth].
2013-04-29 DP 1.18.0 Add an option to include column headers when copying
from the query tool results [Jasmin Dizdarevic].
2013-04-29 DP 1.18.0 Allow the decimal mark displayed by the query tool to be
configured as the thousands separator can [Jasmin
Dizdarevic].
2013-04-25 DP 1.18.0 Ensure the Query Tool's maximum column length setting
is honoured.
2013-04-22 DP 1.18.0 Handle default privileges to PUBLIC correctly. [Dhiraj
Chawla].
2013-03-24 GL 1.18.0 Add tab option in the Import dialog. Per a request from
Jeff Janes.
2013-03-17 GL 1.18.0 Add smallserial handling. Per a request from Matthew
Syphus.
2013-03-01 DP 1.18.0 Fix the editing of pg_hba.conf files [Dhiraj Chawla].
2013-02-25 DP 1.18.0 Fix the display of extension owner names.
2013-02-23 GL 1.18.0 Add a title to the backup and restore windows. Per
request from Bastiaan Olij.
2013-02-22 DP 1.18.0 Fix a bug that could cause a NOTICE to be displayed
when rendering FTS Configurations in the tree.
2013-02-07 DP 1.18.0 Don't try to display dependents or dependencies for
pgAgent jobs, schedules or steps.
2013-02-06 DP 1.18.0 Fix the handling of expiry times when modifying roles.
2013-02-04 DP 1.18.0 Prevent foreign keys being recreated unnecessarily when
modifying tables [Michael Banck]
2013-01-24 DP 1.18.0 Prevent Cmd+S adding characters to the Query Tool when
the Save button is disabled.
2013-01-18 DP 1.18.0 Fix handling of Greenplum partitions [Lubomir Petrov]
2013-01-06 GL 1.18.0 Add -V/--version CLI option.
2013-01-06 GL 1.18.0 Add actions menu to the serverstatus tool.
2013-01-06 GL 1.18.0 Fix the database SQL when reseting a configuration
parameter. Per a report from Bartosz Dmytrak.
2013-01-04 GL 1.18.0 Refresh the toolbar buttons when a list has been
updated. Per a report from Evan Martin.
2013-01-04 GL 1.18.0 Fix the "NO INHERIT" query. Report from Thomas Joseph.
2012-12-24 GL 1.18.0 Display default privs. Report from Nathan Alden.
2012-12-24 GL 1.18.0 Sort references by schema name and relation name in
dlgForeignKey. Report from Michal Kozusznik.
2012-12-24 GL 1.18.0 Fix the change of the superuser attribute. Report from
Michal Kozusznik.
2012-12-18 DP 1.18.0 Prevent a crash when using Cmd-A on a file loaded into
the Query Tool when opened with Cmd-E on Mac.
2012-12-07 DP 1.18.0 Fix the queries used to get object comments to allow
for duplicate OIDs that may be present following use
of pg_upgrade.
2012-12-03 DP 1.16.1 Prevent a crash that could happen if further changes
were made on a dialogue after using the Apply button.
[Akshay Joshi]
2012-11-29 GL 1.16.1 Save new comments on already existing columns when
editing a table. Per a report from Jeff Janes.
2012-11-29 GL 1.16.1 Fix the query editor behaviour when executing COPY TO
stdout and COPY FROM stdin [Heikki Linnakangas]
2012-11-28 AV 1.16.1 Date picker controls returns a full timestamp by
default, which can cause inadvertent date changes
on jobs and role validty dates. Ignore the time part.
2012-11-26 MH 1.16.1 Fix query for database descriptions
2012-11-15 DP 1.16.1 Avoid querying the catalogs for toast table settings
for every table in the database. This gives a huge
performance gain with large schemas.
2012-11-08 DP 1.16.1 Prevent a crash when refreshing a node which has a
child with an open dialogue [Dhiraj Chawla]
2012-11-08 DP 1.16.1 Fix dropping/renaming of indexes [Akshay Joshi]
2012-11-08 DP 1.16.1 Avoid updating the GQB model on every key press in
the query tool [Dhiraj Chawla]
2012-11-02 DP 1.16.1 Fix a crash that can occur when renaming objects.
[Ashesh Vashi/Sachin Srivastava]
2012-11-01 DP 1.16.1 Fix dropping of constraints [Akshay Joshi]
2012-10-31 DP 1.16.1 Fix the "blocked by" column in the server status
dialogue on 9.2 servers [Sachin Srivastava]
2012-10-11 DP 1.16.1 Prevent a crash if the query tool is closed whilst a
file is loading [Akshay Joshi]
2012-10-09 AV 1.16.1 Fix setting of comments on PPAS procedures.
2012-10-08 DP 1.16.1 Don't autosize the search results columns if no
results are found [Akshay Joshi]
2012-10-08 AV 1.16.1 Prevent a crash if opening a second config file in
the editor.
2012-10-08 DP 1.16.1 Prevent the SSL options combo box displaying
duplicate options if the server dialogue is
reopened [Akshay Joshi]
2012-09-14 GL 1.16.1 Fix trigger query when connected to PostgreSQL 8.2 or
lower, per a report from Jon Roberts.
2012-09-12 GL 1.16.1 Fix message when executing an empty query, per Marc
Mamin.
2012-09-06 DP 1.18.0 Detect serial/bigserial columns from pg_depend, rather
than guessing [Quan Zongliang].
2012-09-05 DP 1.18.0 Display the next expected value for a sequence in the
property list [Quan Zongliang].
2012-07-11 MH 1.18.0 Add optional thousands separator to the query tool
results grid.
2012-07-11 MH 1.18.0 Right-justify numeric values in the query tool results
|
|
## Rails 3.2.14 (Jul 22, 2013) ##
* Do not re-create destroyed association when saving the parent object.
Fixes #11450. *Paul Nikitochkin*
* Do not shallow the original exception in `exec_cache` on PostgreSQL adapter.
Fixes #11260. *Rafael Mendon«®a Fran«®a*
* Fix `ActiveRecord::Store` incorrectly tracking changes of its attributes.
Fixes #10373. *Janko Marohni««*
* Fix a bug that prevented the use of the default STI inheritance column
(ActiveRecord::Base.inheritance_column = 'some_column'.)
*chapmajs + Takehiro Adachi*
* Fix mysql2 adapter raises the correct exception when executing a query on a
closed connection. *Yves Senn*
* Fixes bug where `Company.new.contract_ids` would incorrectly load
all non-associated contracts.
Example:
company = Company.new # Company has many :contracts
# before
company.contract_ids # => SELECT ... WHERE `contracts`.`company_id` IS NULL
# after
company.contract_ids # => []
*Jared Armstrong*
* Fix the `:primary_key` option for `has_many` associations.
Fixes #10693. *Yves Senn*
* fixes bug introduced by #3329. Now, when autosaving associations,
deletions happen before inserts and saves. This prevents a 'duplicate
unique value' database error that would occur if a record being created had
the same value on a unique indexed field as that of a record being
destroyed. Backport of #10417
*Johnny Holton*
* Fix that under some conditions, Active Record could produce invalid SQL of
the sort: "SELECT DISTINCT DISTINCT". Backport of #6792. *Ben Woosley*
* Require `ActiveRecord::Base` in railtie hooks for rake_tasks, console and
runner to avoid circular constant loading issues. Backport #7695.
Fixes #7683 and #882
*Ben Holley*
* Maintain context for joins within ActiveRecord::Relation merges.
Backport #10164. *Neeraj Singh + Andrew Horner*
* Make sure the `EXPLAIN` command is never triggered by a `select_db` call.
*Daniel Schierbeck*
* Revert changes on `pluck` that was ignoring the select clause when the
relation already has one. This caused a regression since it changed the
behavior in a stable release.
Fixes #9777.
*Rafael Mendon«®a Fran«®a*
* Confirm a record has not already been destroyed before decrementing
counter cache. *Ben Tucker*
* Default values for PostgreSQL bigint types now get parsed and dumped to the
schema correctly. Backport #10098. *Erik Peterson*
* Removed warning when `auto_explain_threshold_in_seconds` is set and the
connection adapter doesn't support explain.
This is causing a regression since the Active Record Railtie is trying to
connect to the development database in the application boot.
*Rafael Mendon«®a Fran«®a*
* Do not reset `inheritance_column` when it's set explicitly.
Backport of #5327. *kennyj + Fred Wu*
* Fix a problem wrong exception is occured
when raising no translatable exception in PostgreSQL. *kennyj*
* Resets the postgres search path in the structure.sql after the structure
is dumped in order to find schema_migrations table when multiples schemas
are used.
Fixes #9796.
*Juan M. Cuello + Dembskiy Alexander*
* Reload the association target if it's stale. `@stale_state` should be nil
when a model isn't saved.
Fixes #7526.
*Larry Lv*
* Don't read CSV files during execution of `db:fixtures:load`. CSV support for
fixtures was removed some time ago but the task was still loading them, even
though later the code was looking for the related yaml file instead.
*kennyj*
|
|
|
|
- Fix uninitialized indicators in conversion_into_type and
conversion_use_type specialisations
- Fixed placeholder matching for PostgreSQL-style casts with ORM
- Fixed memory leaking in use binding in case of bind/unbind sequence
- Fixed sscanf formatter for MinGW/MSVC in backends
- Fixed partial placeholder name matching for ORM cases
- Added test for use of indicators with rowset<row>
- Added test for get_affected_rows after bulk operations
Add options for selecting MySQL/PostgreSQL/SQLite backends, defaulting
to PostgreSQL.
|
|
* Shared Libraries are now named so as to allow having multiple versions of Slony installed simultaneously on a database cluster
* Let DDL for EXECUTE SCRIPT to be specified inline
* Added a RESUBSCRIBE NODE command to reshape clusters.
* The FAILOVER process has been reworked to be more reliable.
* Major "protocol" change; rather than constructing cursors to query logged updates, version 2.2 now uses the COPY protocol to stream data into log tables on subscribers.
|
|
|
|
* Add materialized views
* Make simple views auto-updatable
* Add many features for the JSON data type, including operators and functions to extract elements from JSON values
* Implement SQL-standard LATERAL option for FROM-clause subqueries and function calls
* Allow foreign data wrappers to support writes (inserts/updates/deletes) on foreign tables
* Add a Postgres foreign data wrapper to allow access to other Postgres servers
* Add support for event triggers
* Add optional ability to checksum data pages and report corruption
* Prevent non-key-field row updates from blocking foreign key checks
* Greatly reduce System V shared memory requirements
|
