Major plans for 2.0 – Firebird support will be added
Milan Babuskov one of original creators of fbManager which became Flamerobin, just made it publicly known that he now works for MySQL AB.
My project, Flamerobin and Firebird Foundation , have been acquired by MySQL, AB. As part of the agreement, I will be working full time for MySQL. I expect to lurk on the flamerobin-devel list from time to time and may contribute the occasional wolf-o-gram, but I will not be taking an active part in Flamerobin development. Although Mariuz will work for MySQL, part time, translating from wolf to English,He will continue to be active in the Firebird/Flamerobin projects.
MySQL acquired IbPhoenix too and Paul Beach will work as MySql marketer.
I do know MySQL’s VP of Marketing…. not surprising
really since we were both at Borland together. And since Zack
joined MySQL a number of other Borland types have appeared…
Steve Curry for PR etc
Today first RC1 release is announced that many oss developers had been awaiting
MyFireGreSql 2.0 is based on code from mysql 6.0 ,firebird 3.0,postgresql 9.0
We needed a big shake up in open source database world and working on the common code base have it’s
advantages:Firebird and Postgresql borrowed from mysql’s speed , mysql used MVCC for it’s transactional engine (is based on firebird) .
SQL2003 is implemented in all three engines now that is published as standard .So why working on a three SQL200X implementations when we could work only on one? , The project’s model is linux kernel where vendors are using only one source code for their distributions (patched properly) but there is only one organization for working on the kernel osdl.
The results are in, and the voters have spoken. We’ve just tallied the
results for the 2006 SourceForge.net Community Choice Awards. The
results are impressive–more than 212,000 of you came to voice your
support for the projects nominated. Winners will be announced at the
Slashdot Lounge in the .ORG Pavilion at LinuxWorld Expo, Boston, on
April 5, and the complete list of winners will be posted on
SourceForge.net on April 6.
Meanwhile, you can view the complete list of nominees and read more
about the awards at:
That link tells of thieves attempting to steal a Koala. What idiots. Surely the only people who think Koalas are cuddly and nice are foreiners who couldn’t know any better.
Turns out, the Koala did so much damage to the would-be thieves that they abducted a fresh water crocodile instead 🙂
[Ed via Robin’s Aussie blog]
I said AGES ago I would post my todo list and the code. So, here it is!
By downloading you agree to the following disclaimer:
This programme carries no warranties either implied or explicit. Use at your own risk. It was written by me as a personal challenge. It seemed to work when I ran it, but it might not work for you. It might also delete random files, send pornographic pictures to the president, crash you computer or cause space aliens to destroy the planet. Use it at your own risk and remember: if it’s not backed up, it’s not important.
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.