Firebird database?

Heya,

I see Firebird pop up more and more on the lists. Anyone using it that loves it for some particular reason?

Firebird packs alot of power in a small db package. I have been dabbling with it (just dabbling) off and on and it is very nice - it is a huge leap forward from mysql. The small package coupled with the power and the windows installation of it make it an ideal replacement for access and filemaker on a windows box and a powerfull replacement for mysql on other boxes. I am hoping to create my next big project around it in the next couple of months. I am also hoping to do a php5/firebird article in the near future...

I'd be interested in reading that article. How would you compare firebird to Postgres?

Well, I can't comment on that as I have really no experience in postgre. I am sure rycamor and RodK can shed some light on this. I know there isn't as many features as prostgre, but that is about all I can add at the moment...

Having used a wide variety of databases over the years, I've found that I can get the job done with just about any of them. This is a good thing because more often than not, I don't get to pick the database I get to use. If I list some of the things I like about Firebird, somebody else could quickly point out that the same feature is available in another database. Database comparisons can sometimes rapidly degrade into a religous argument because everyone has their favorite.

Having said that, here's some things I like about Firebird. (I'm not saying these features are unique or special. I just find them useful.)

• I use Borland C++ Builder. Firebird is based on Interbase so the two tools work well together. Much of Borland's examples, documentation and controls use Interbase. They're a good fit.
• I use stored procedures a lot. I can define my own Exceptions based on my business logic, store them in the database and raise them by name in the SP.
• Before/After Triggers
• Domains - I can create "new" datatypes like "Money" or "SerialNbr" that are of a particular base type with a default value, constraints, etc.
• Events. When a particular event occurs, I can have a trigger or stored procedure raise an Event. The Event Manager can then asynchronously notify applications who have subscribed to the event that a database change has occurred without the external applications having to constantly poll the database. (I haven't implemented this in a program yet but I can think of some situations where it will be useful)
• Unique and Primary Keys. Referential integrity that can include cascading updates and deletes. Check constraints for field values in a record.
• Multiple database access with distributed two-phase commit. A transaction must commit on all the servers or will be rolled back across all servers.
• Database shadows. A real-time copy of the database.
• Generators. You can create as many number generators as you want. They can be used to automatically assign autonumbers to table records. Or you can call a generator from your program to get the next number in a sequence. Useful in key generation.
• The database can be distributed as either a server or in classic mode. Classic mode allows you to develop desktop applications that access the database directly as a local file (like Microsoft Access).
• Read-only databases. This can be useful for desktop applications where you want the database to be distributed on a CD and accessed locally via classic mode.
• Really good support from their forums. The developers are very active in answering questions. You can ask Firebird questions on Borland's Interbase newsgroups.
• It was real easy to install and work with.
• I bought a commercial tool called Database Workbench that's made working with the database real easy. See the attached screenshot. (http://www.upscene.com/products.htm)
• Good documentation. All 7 of the Interbase 6.0 volumes as .pdf files (~2,000 pages).

The bottom line is this database does everything I need, runs on all the platforms I program on and has been easy to use. Like every database it has its little quirks, but so far it isn't missing a feature I can't live without. I'm not a guru yet, but the more I use it, the more I like it.

If you haven't been to this page, you might want to look over it: http://firebird.sourceforge.net/ind...id=ib6_overview

I thought Firebird was a web browser not a database

You're joking about a sore spot there buddy. The naming conflict is not funny at all...well maybe a little because its gotten so absurd it's like a soap opera.

Couldn't resist making that troll post

It has played out like a soap opera though, "Oh, it's only a codename, didn't we mention that before." Its just stupid.

(Note: As has been said before, no thread in the Lounge is allowed to stay on topic )

then i like cookies

Sorry to break the news to you but they're about to outlaw Oreos. You're going to have to drive to the bad part of town and buy them off a street corner.

http://www.msnbc.com/news/912868.asp

Oh my gosh, black market oreos

Well, interestingly enough, I guess I asked about Firebird DB probably because of how much has been mentioned of late regarding the naming conflict with the Mozilla group.

So despite it being silly that there is such a problem with a name, especially considering the intellectual work it takes to develop these applications, it does bring both sides into the spotlight a little bit.

Thanks for the input regarding Firebird DB. I pretty much stick with MySQL, but I will keep it in mind for future projects. It's great to see competing (in a healthy way
) applications within the Open Source community.