Lazarus Release Candidate 1 of 1.2 and Stable 1.0.14
The Lazarus team would like to announce the first Release Candidate for the upcoming Version 1.2.
Also a bug fix release Lazarus 1.0.14
Author: mariuz
http://wiki.ubuntu.com/Mariuz
Firebird ActiveRecord gem is updated to version 0.8.0 with support for Rails 4
Firebird ActiveRecord adapter 0.7.9 for Rails 3.2+ released
An update about embedded Firebird on iOS
An update about embedded Firebird on iOS, a new build is available that fixes a problem in how the bin directory located the firebird.msg file etc. A new function realpath added to config_root.cpp for darwin now returns the canonicalized absolute pathname.
Firebird backend Beta 1 for Django 1.6 is released
Maximiliano Robaina announced django-firebird 1.6 beta
A few days of the Django 1.6 was released, django-firebird is now in beta 1 stage. Feel free to fork from master branch or download and try it.
Remember that is using fdb as a default driver.
Any feedback is welcome.
Detailed schedule of Firebird seminar “All About Transactions” is available
Alexey Kovyazin announced:
Detailed schedule is here http://firebirdsql.org/en/firebird-tour-2013-details/
Several seats are still available both in Siegburg (November 22) and Prague (November 25).
Firebird 2.5.2 Update 1 for all Ubuntu releases is uploaded into Firebird stable ppa
Here you can find the latest stable release Firebird 2.5.2 Update 1 for all supported Ubuntu releases.
Follow the Firebird 2.5.x guide for usage and installation.
What is changed is added the security fixes plus many fixes from Debian unstable repository.
Compared with previous upload support for hardy and oneiric is dropped (unsupported by Canonical)
Jaybird 2.3 will become Jaybird 3.0
Mark Rotteveel announced :
As Jaybird 2.3 is going to be a big change from Jaybird 2.2, I have
decided to renumber the version to Jaybird 3.0.
Changes planned for Jaybird 2.3 are now planned for Jaybird 3.0. Changes
planned for Jaybird 3.0 are now planned for Jaybird 3.1 (but might get
into Jaybird 3.0).
Some of the major changes include a new Type 4 (wire protocol)
implementation to be able to support new features in the wire protocols
(especially for Firebird 3*), and probably also in the Type 2 (native)
implementation. The behavior and compatibility of Jaybird and the
interpretation of the JDBC specification might (will) also change for
some cases and I think a new major version is needed to indicate this,
as I expect that this new version will not be a drop-in replacement in
all cases.
There is no date set for the release of Jaybird 3.0, work is progressing
but slowly and the changes made for the new wire protocol implementation
will cascade through the entire driver once I replace the existing
implementation.
Once the new wire protocol implementation is in place I will start
releasing snapshots for testing.
Development of Jaybird 2.2.x will continue at least until the release of
Jaybird 3.0. If necessary new features will be implemented and bugs will
continue to be fixed. For example Firebird 3 BOOLEAN type and (basic)
Java 8/JDBC 4.2 support will be added in Jaybird 2.2.4.
I have planned to release Jaybird 2.2.4 at the end of this month.
*: Actual implementation for the Firebird 3 authentication and
encryption protocol (SRP) is not yet planned for Jaybird 3.0.
Firebird ActiveRecord adapter 0.7.8 for Rails 3.2+ marked as stable
Although this adapter may not yet have feature parity with the 1st tier databases supported by the Rails developers,
it has been in production for several months without issues (Rails 3.2.x) and may be considered stable. (Rails 4 testing and pull requests are wellcome)
eHealth system demo up and running (powered by Firebird)
Nigel Weeks created a demo for an assignment (for his Paramedic Practice degree) for a small fictional town’s health clinic, some appointment rooms, and some remote health professionals that are employed a few days a week (You can check it online also download the source code : Firebird SQL , PHP , webrtc, Ubuntu Server):
Naturally, I used the tools I know and love: PHP, FirebirdSQL, a splash of CSS, and a dollop of HTML.
Its feature set:
-Client management, current and outdated contact information(historical support)
-Bookings to see specialists, and notes system to go with the consultancy
-Booking screen with calendar for each specialist, and automatic blocking out for longer appointments.
-Daily run sheets for specialists (so they can see their appointment load in the morning)
-Payment status reports on appointments
-Reports on Specialist’s booking loads, and booking trends for hour of the day
-Outstanding account reports
-A WebRTC TeleHealth system for remote client and specialist consultancy and more. Oh yes, role-based access control(rudimentary)