ANN: FB TraceManager V2.5.4 available (Trace SWEEP)

Upscene Productions is proud to announce FB TraceManager V2.5.4, a professional environment to monitor, profile, trace and optimize Firebird databases.

More information on the new release is available here:
http://www.upscene.com/displaynews.php?item=20120731b

This release adds support for the new Firebird 2.5.2 sweep tracing capabilities via the Trace API across the entire product (trace configuration “log_sweep”, parser, trace data storage etc.).

A ~ 4min. screencast is available here:
http://ts.upscene.com/download/demos/fbtm/fbtm_sweep_tracing.htm

More information on the product is available in the FB TraceManager section on our website, including an edition comparison sheet, webcasts etc.:
http://www.upscene.com/go/?go=fbtm

Django 1.4 support for Firebird ready for tests

Maximiliano Robaina wrote on django-firebird group

I would just like to say that the first attempt to support django 1.4 is ready for test, but we have a few considerations related to this release.

First, this test version live in  github.com/maxirobaina/django-firebird
For now, this repo is just for test but I think that will be the next official home in short time.

Second, the way as insert worked was deprecated. At previous versions we have contemplated not to use triggers for manage auto incremental fields, the value of autoinc fields were generated on python code by using GEN_ID or NEXT VALUE FOR according to firebird version. Now, is necessary to have triggers (and sequences/generators) for inserts and set new primary key values, then, if you are using a legacy database without this, It will not work.
If anybody think that is a bad idea remove this behavior and need it, we can discuss about it.

Third, obviously django-firebird doesn’t pass all the django test suite.
For example, django try to create a field as decimal(38,30)

django.db.utils.DatabaseError: (-842, u’isc_dsql_prepare: \n  Dynamic SQL Error\n  SQL error code = -842\n  Precision must be from 1 to 18 — CREATE TABLE “MODEL_FIELDS_BIGD” (\n    “ID” integer NOT NULL PRIMARY KEY,\n    “D” decimal(38, 30) NOT NULL\n)\n;’)

And of course, we need to have our own test suite.

That is all. Feel free to try and to express your opinion.

Jaybird 2.2 #JDBC #Java driver is Released with many fixes

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.0.

This release contains the following changes:

  • Enhanced support for JDBC 4.0 (Java 6)
  • Support for JDBC 4.1 (Java 7) — including try-with-resources support,
  • Implementation of getGeneratedKeys(),
  • Enhanced support for the services API,
  • Support for 64 bit native libraries for Type 2 / Embedded,
  • A number of bug fixes.

Fixes since Jaybird 2.2.0-beta-1:
* ConcurrentModificationException when closing connection obtained from org.firebirdsql.ds.FBConnectionPoolDataSource with statements open (JDBC-250),
* Memory leak when obtaining multiple connections for the same URL (JDBC-249),
* CPU spikes to 100% when using events and Firebird Server is stopped or unreachable (JDBC-232),
* Events do not work on Embedded (JDBC-247),
* Provide workaround for characterset transliteration problems indatabase filenames and other connection properties (JDBC-253),
* FBBackupManager does not allow 16kb page size for restore (JDBC-255),
* Log warning and add warning on Connection when no explicit connectioncharacter set is specified (JDBC-257).

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.0</version>

The artifactId depends on your target Java version: jaybird-jdk15, jaybird-jdk16 or jaybird-jdk17.

FlameRobin connection thread test on Windows

I have posted a test version of FlameRobin: http://mghie.users.sourceforge.net/flamerobin_win32_test.zip

(a ZIP file containing only the 32 bit executables for Windows in ANSI and Unicode version) that uses a thread to establish the database connection. That
means that the progress dialog can be moved and cancelled, and the progress bar is updated in indeterminate mode. To see it in action it’s
best to try to connect to a database on a server which is not available or which doesn’t exist, which so far blocks FlameRobin completely until
the connection call times out. It would be great if people could test this and write (to flamerobin-devel) whether anything

breaks for them (it didn’t for me, yet). I’m a little of unsure if I should clean this up and commit…

Thanks


Michael Hieke

1 52 53 54 55 56 147