DRoster 2.2.1 provides businesses and organizations of all sizes and needs with the flexibility required to create unique schedules, rosters, and shifts. Driven by a rule-based engine, DRoster validates schedules and availability times instantly preventing costly and time-consuming clashes and errors in scheduling. It uses a standard Software industry database (Firebird) to enable integration of DRoster with other data sources and applications. More information here.
From Dmitry Yemanov:
Consider it a bughunting success story 🙂
Some time ago we’ve got a bugreport about bugcheck #205 (index bucket overfilled) appearing during the database restore on a v2.0 server. The database was big and it was hard for the customer to create a test case. Fortunately, a special build with improved tracking facilities helped and the bug has been found and fixed. So far so good.
But a few weeks later, this bug reappeared on the same database and under the same conditions. The only difference was a database size which has grown. After unsuccessful attempts to find the bug, the reduced copy of the customer database (with just a single table that causes the problem) has been received. It reproduced the bug successfully, with just one minor issue… it was a 3.5GB backup file 🙂 The restore process takes 6 hours in the debugger. It required a few runs to figure out the actual problem (don’t ask me how many days it has taken :-), but it has been finally fixed. Sigh. Some bugs are buggier than others 🙂
By the way, this should be exactly the bug that prevented Dalton Calford from restoring his database on v2.0 (he reported the issue in fb-devel).
From Dmitry Yemanov:
RC1 has just been released. There will definitely be RC2 as well, as we have to complete the documentation and solve some minor installation issues. Also, there were a few regressions fixed in the meantime.
But should one expect RC3 and so on? This depends on you only. The better you test the server and provide us with the feedback, the sooner we release the final version.
The release branch will be created the next week. At the same time, we should publish the updated roadmap to reflect the actual state of development. I also expect some private branches to be merged with HEAD as soon as it’s unlocked to allow the new code.
Knoda is a KDE database-frontend for DBase, Firebird, MSAccess, MySQL, Paradox, PostgreSQL, SQLite, and ODBC.Besides tables, views, and queries, it also handles forms
Release focus: Major feature enhancements
The main new feature is the improved query editor. It handles outer and inner joins (as far as the SQL server supports it). The drivers SQLITE3, SQLITE2, and MDB (MS Access) can compile without the need to install extra packages, so they are generally available. Many bugs are fixed.
The Firebird Project is pleased to announce the release of the first release candidate of Firebird 2.0, for final testing. Download kits are available for Windows and Linux, including x64 Linux. However, due to hardware failure on the Windows build system, there will be initial delays in accessing the Win32 kits. Patience please!
We’ve uploaded several “get in touch” flash movies for the IB LogManager product family.
If you have never heard about IB LogManager or if you are fearly new to our IB LogManager product line, then they might get you started more efficiently.
Even experienced IB LogManager users might benefit from the following demos. If you want to give IB LogManager yourself a try, then feel free to download a trial version here:
It makes sense to watch them in the following order (watch the wrap!):
– Preparing a database (~ 5:35 min)
– Logging schema definition (~ 8:10 min)
– Browsing log data (~ 12:40 min)
– Productivity tools (~ 5:23 min)
– IBLMPump utility (~ 16:07 min)
– IBO Global DML caching (~ 8:57 min)
The font got a bit small. If you are using a higher resolution than 1024×768, then please give the following a try:
20GB of video data available, with around 100 hours of firebird related presentations from Firebird Conference
There is currently about 20GB of video data available, with around 100 hours of firebird-related presentations from last two Firebird Conferences and other events.
Here is the list of available Films
What is IBExpertLive?
HK-Software has implemented a streaming system based on the Firebird database server, which publishes pictures and audio, as needed to view the presentations from the 2004 and 2005 Firebird Conferences. We will also be adding IBExpert tutorial videos enabling you to learn more about working with Firebird and InterBase with IBExpert.
To use IBExpertLive, you need a firebird connection via Internet using port 13050 to our server on IP 22.214.171.124. If it does not work, please check your firewall settings. For reporting any other questions/problems regarding IBExpertLive, please use the following contact addresses:
IBELive newsgroup: hk-software.ibexpert.live (English, German and Russian language).
E-mail: ibexpertlive at ibexpert.biz.
There might be some videos that are not working yet, even if they are on the list. Please bear with us; we’ll have everything up and running as soon as possible.
The download address is: www.ibexpert.com/ibexpertlive/IBExpertLive_setup.exe
The Firebird SQL data application block is intended to speed up development, and it should be used in conjunction with data layer classes in much the same way as Microsoft’s data block. The sample included with this article uses the embedded Firebird SQL database (included in sample) to demonstrate the use of the application block without having to bother setting up a database.
Firebird SQL data application block was inspired by the Microsoft Application blocks. The block provides overloaded methods to query a Firebird database which return a dataset, data table, or integer in the case of scalar database calls. An additional overload method takes an existing dataset as a parameter and fills the results of a stored procedure send as parameter as well.
Ruby on Rails is out with a new release of its open source Web framework with a promise: making it even easier to develop AJAX (define)-based, Web 2.0 applications. RoR needs a database to run (either MySQL, PostgreSQL, SQLite, Oracle, SQL Server, DB2, or Firebird) and the Apache HTTP Web server. Read more.
For those who are on Linux and want to extract database’s metadata, please have a look to firebird/interbase native isql tool, that permits to export DDL as follow:
isql DBalias -o ddl.sql -x -u SYSDBA -p masterkey
PAscal on fyracle newsgroup