ANN: #Ruby Sequel 3.28.0 is Released

Sequel 3.28.0 has been released and should be available on the gem mirrors.
What is changed on the firebird driver :

  • The firebird adapter has been split into shared and specific parts,
    and quite a few fixes were made to it.
  • A jdbc firebird subadapter has been added, allowing connection to
    firebird databases from JRuby.
  • The firebird adapter was substanially modified, specifically parts related to insert returning autogenerated primary key values, so if you were previously using the adapter you should probably take more care than usual when testing your upgrade.

Firebird 2.5.1 is officially released

Firebird Project is happy to announce general availability of Firebird 2.5.1 This sub-release introduces several bug fixes and many important improvements – for example, performance improvements during a database restore, the ability to write to global temporary tables in read-only databases, etc. For the full list of changes please refer to the Release Notes, Chapter 2 “New in Firebird 2.5”. Firebird 2.5.1 has 100% compatible on-disk structure with Firebird 2.5.0, so it is recommended to migrate to 2.5.1 as soon as possible.

There is a substantial number of bug fixes, this sub-release takes in a few minor improvements and optimizations that missed the initial release. In summary:

  • Significant for MacOSX 10.7 users was a bug that caused attempts to start Superserver and Superclassic to fail. The bug is described in Tracker ticket CORE-3589 and also in the Bug Fixes list for this sub-release.
  • An SQLSTATE context variable is now available in PSQL, parallel to the the context variables GDSCODE and SQLCODE that are used in WHEN blocks to test for error conditions.
  • A couple of improvements were made, that should help performance when global temporary tables (GTTs) are being used:
    • The “undoing”, on rolling back the transaction, of changes made to GTTs that were created with the ON COMMIT DELETE ROWS option was an unnecessary overhead and has been bypassed.
    • Garbage collection in global temporary tables was being delayed unnecessarily by active transactions in other attachments. That bottleneck is gone.
  • A needed optimization in the temporary space manager with regard to small chunk allocations has been implemented.
  • The Lock Manager has been provided with the capability to cancel waiting, avoiding a condition whereby a transaction in WAIT mode could wait interminably for the end of another transaction that could not be achieved by either a DELETE FROM MON$xxx or an fb_cancel_operation request.
  • The query optimizer now estimates the actual record compression ratio, enabling better guesses about the number of stored records in tables.
  • Some minor improvements to the remote interface:
    • Any unused bytes of varchar values in the message buffer are now set to zero.
    • Set the SO_KEEPALIVE option on the client TCP socket
  • The MON$STATEMENT_ID value constant is now kept constant among monitoring snapshots.
  • Ports of this sub-release were done for Linux/HPPA and Linux/alpha platforms.

Episode 1: Fishbowl Database Security Basics (application that uses Firebird)

Here are the security notes for an application that uses Firebird:

Another thing to keep in mind while securing your database: sometimes when we release new versions of Fishbowl, it upgrades your database to a new version, as well. When this happens, Fishbowl makes two different backups. One is a copy of the database; the other is a Firebird database dump. I like to call these the “Murphy’s Law backups” because you shouldn’t need them, and you won’t need them – until you don’t have them. They are created for rollback purposes during the upgrade. Leaving these unprotected is just as bad as leaving your main database unprotected. You can find these files in C:\Program Files (x86)\Fishbowl\database\data – inside the “old” and “backup” directories.

Perl driver DBD::Firebird 0.7.0 released

This release brings many changes and docs cleanup

  • use standard ROWS alternative to Mysql LIMIT
  • In firebird 2.5.x standard way is to use sequences
  • dialects cleanup
  • tests-setup: avoid passing credentials on the command line
  • link with libfbembed if given a special environment variable
  • fix missing database check during tests
  • test 81-event-fork.t when linked with libfbembed
  • implement add ib_enable_utf8 dynamic attribute
  • remove $Id$ markers from CVS/Subversion
  • add test for RT#55244
  • test 47-nulls.t: ensure inserting undef in a non-null field fails
  • fix $dbh->do() and $sth->execute() to properly return the number of affected records
1 120 121 122 123 124 294