Slashdot Mirror


Firebird Relational Database 1.5 Final Out

firebirdy writes "The Firebird Project is pleased to announce that the v1.5 release of the Firebird database engine is now available for immediate download. The v1.5 release represents a major upgrade to the engine, which has been developed by an independent team of voluntary developers from the InterBase(tm) source code that was released by Borland under the InterBase Public License v.1.0 on 25 July 2000. Development on the Firebird 2 codebase began early in Firebird 1 development, with the porting of the Firebird 1 C code to C++ and the first major code-cleaning. Firebird 1.5 is the first release of the Firebird 2 codebase. Install packages are currently only available for Windows and Linux but other platforms should follow shortly." This product is not to be confused with newly renamed Firefox web browser, which was also called Firebird for some time.

445 comments

  1. Bleh by CeleronXL · · Score: 4, Insightful

    The only reason anyone even knows about them anyway is because of the former Mozilla Firebird. :O

    1. Re:Bleh by CeleronXL · · Score: 3, Insightful

      Flamebait? Maybe. I don't think there's enough support of the FirebirdSQL system here to really be a successful bait of any flame. Though of course what I said is very true, regardless of whether or not it's negative towards the FirebirdSQL people. They gained incredible publicity through this. It's doubtful that this news post would be here today had it not been for the naming conflict, because no one would even care.

    2. Re:Bleh by Anonymous Coward · · Score: 4, Informative

      Wrong. This is a fine database that was built from the once open-sourced Borland Interbase. Anybody working with free databases should know it (people who are comparing it to MySql: is mysql a *real*, relational, transactional database server? stored procedures? triggers? foreign keys? )
      Related to the naming issue: the mozilla people choosed a name that was already taken by another project, they changed their name now, and that's it...

    3. Re:Bleh by fm6 · · Score: 3, Informative

      Firebird has a few minor claims to fame. The big one is that it's a real relational DBMS, not an ISAM driver with a pseudo-relational front-end.

    4. Re:Bleh by jejones · · Score: 4, Funny

      I think the writers of the Firebird BBS would have something to say about who chose a name already taken by another project.

    5. Re:Bleh by Anonymous Coward · · Score: 0

      That is right. YOU don't think.

      Some of us are using it in major commercial software projects.

      It is certainly an adequate replacement for Microsoft SQL Server.

      If you don't have a clue what you are talking about, feel free to refrain from posting.

    6. Re:Bleh by Anonymous Coward · · Score: 5, Informative

      Firebird has a few minor claims to fame.

      What about distributed transactions? AFAIK, no other open source relational database supports them (neither PostgreSQL, nor MAXDB, nor MySQL). I do quite a bit of distributed object programming, so I can't do without distributed transactions, and Firebird's work well.

      What about server-side event notification? AFAIK PostgreSQL is the only other open source relational database that supports them. Switching from a polling architecture to event notification can yield huge performance benefits.

      What about nested transactions? Firebird 1.5 supports savepoints, which are a basic rendition of nested transactions. AFAIK, MAXDB is the only other open source relational database with nested transaction support (though MAXDB's are full-fledged nested transactions, not just savepoints).

      This isn't just some Firebird-propaganda-bullet-list. I find all these features indispensable.

    7. Re:Bleh by Anonymous Coward · · Score: 0

      I wish CeleronXL would refrain from posting. 90% of his history is 1-liner trolls and failed attempts at first posts.

    8. Re:Bleh by fm6 · · Score: 0, Offtopic

      An informative post. Pity you made it as an AC!

    9. Re:Bleh by HarrisonFisk · · Score: 2, Informative

      It is worth noting that MySQL with InnoDB has supported SAVEPOINT's now for a few versions. [code]http://www.mysql.com/doc/en/Savepoints.html[ /code]

    10. Re:Bleh by Anonymous Coward · · Score: 0

      Servoy is currently based on FireBird for its repository data but will connect to anything. I don't see anybody bringing up Servoy, is anybody familiar with it? Seems like a pretty good multiplatform database development environment to me.

    11. Re:Bleh by marcovje · · Score: 2, Insightful

      Nobody are the amateurs, and the Slashdot wannabee ha4ors. They also don't get that this is the only commercial grade db system available for free. (and no, mysql doesn't live up to that).

      Professionals would already know Interbase (Firebirds previous name). It's the main database technology behind Delphi, which is still the best selling bulk development tool after Microsoft's stuff. And the only major commercial development tool with a Linux version.

    12. Re:Bleh by Sxooter · · Score: 2, Insightful

      If Firebird is the only free commercial quality database, why isn't it running the .org and .info domains?

      There is a free database running those domains, but it ain't MySQL or Firebird.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    13. Re:Bleh by carnivore302 · · Score: 2, Interesting

      So firebird is a *real* database? Then why can't it handle databases larger than 80GB?

      Upon advise of a consultant, we trried switching from mysql to firebird for our 250GB, 1.2 billion rows database. We couldn't even import it. After some discussion with the designers of firebird it became evident that firebird has a problem with anything larger than 80GB.

      We went back to mysql, and are very happy with it.

      --
      Please login to access my lawn
    14. Re:Bleh by noisehole · · Score: 2, Interesting

      firebird is a remarkable product. period. hats off to the developers!

      i've been developing commercial software since 93 with borland delphi. delphi is a fine ide with awesome db powers. it came a long way with that crappy paradox/bde thing with a bunch of drawbacks, but interbase is a professional and very powerfull dbs with its sql dialect.

      the firebird project forked back in 2000 as interbase became opensource. as it is licensed under a gpl incompatible license there will always be flaimbaits. especially here on /.

      sure, it got alot of attention due to the name conflict, but software developers that rely on a powerfull and stable db engine surely know about it for a long time.

    15. Re:Bleh by marcovje · · Score: 1


      If you knew something about databases, you would answer that yourself.

      All databases have their niche. mysql can serve read-only data pretty fast. typical use: dumb website backend

      postgresql is a bit better all round, while keeping some performance when it gets simple.

      firebird (or oracle) can handle really complex loads with complex transactions decently.

      Something like the domains is a specialistic task,
      and though I doubt they pick the domains database on a pure ulitarian basis, easy to use application connenctions and complex transactions are not really an item there :_)

    16. Re:Bleh by unixformat · · Score: 0

      Yeah and it appears the old Mozilla Firebird team didnt even know the Firebird database existed before Mozilla used the name Mozilla Firebird for the open source browser.

    17. Re:Bleh by Anonymous Coward · · Score: 0
      Berkeley DB is running .org and .info now?

      :-P

    18. Re:Bleh by Sxooter · · Score: 1

      So, name me a complex load or transaction set that Firebird can handle that Postgresql can't?

      Or are distributed transactions the defining keypoint of a "commercial grade" dbms?

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    19. Re:Bleh by Anonymous Coward · · Score: 0

      Hell, it'd still be a much better choice than MySQL.

    20. Re:Bleh by Kent+Recal · · Score: 1

      Holy batman, 80GB on mysql?
      Brave guy.

    21. Re:Bleh by sql*kitten · · Score: 1

      It is worth noting that MySQL with InnoDB has supported SAVEPOINT's now for a few versions.

      What happens in MySQL if you rollback a transaction that spans InnoDB and MyISAM tables?

      (This is a rhetorical question).

    22. Re:Bleh by HarrisonFisk · · Score: 1

      It will rollback the InnoDB parts, without being able to rollback the MyISAM part. However it will give you a big error saying something like:
      mysql> rollback;
      ERROR 1196: Warning: Some non-transactional changed tables couldn't be rolled back


      I don't know nor have I ever met anyone that has done this by accident (except during development). I do know some that do it on purpose in production though, such as using MyISAM for auditing information, which should always be there, even if a transaction fails.

    23. Re:Bleh by sql*kitten · · Score: 1

      I do know some that do it on purpose in production though, such as using MyISAM for auditing information, which should always be there, even if a transaction fails.

      We can do this in Oracle too, using a trigger with an autonomous transaction. A developer, especially on a large project, shouldn't have to know or care anything about physical storage.

      MySQL is a fine substitute for the ODBC CSV driver... but Firebird, SAP/DB and Postgres cost the same and are decades ahead in functionality.

    24. Re:Bleh by HarrisonFisk · · Score: 1

      If you don't want to care about table types, then they don't have to. You can set the default table type to whatever you want. So if you set it to InnoDB, then they will always have InnoDB tables unless they override it.

      Also one would argue that people already do know about physical storage, that the golden rule of relation theory is already broken. Specifying things such as Indexes and column types already are breaking that golden rule. Why do they exist then? Because of physical limitations that don't exist in pure relational theory. If you can get better performance by adding an index, will you do so?

      It is the same sort of thing if features can be turned off in a database. You have to know if they are on or not before you can use them, the same thing applies in this case.

      Also worth noting that afaik, none of the databases you listed there have autonomous transactions.

    25. Re:Bleh by leandrod · · Score: 1
      > is mysql a *real*, relational

      Neither is Firebird, because it is SQL.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    26. Re:Bleh by leandrod · · Score: 1
      > it's a real relational DBMS

      Nope, it's SQL.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    27. Re:Bleh by fm6 · · Score: 1

      What's your point?

  2. This project by aliens · · Score: 5, Interesting

    Just kind of curious if anyone would care at all if there hadn't been the big stink with the name conflicts.

    I mean, has anyone used this database? Is it really of any note that v1.5 is out?

    --
    -- taking over the world, we are.
    1. Re:This project by CeleronXL · · Score: 1

      I don't think there's enough support for it elsewhere, such as in PHP, for it to be all that useful.

    2. Re:This project by silex_reloaded · · Score: 0

      And is there a convincing reason for some developers to spend a few years of their valuable time making yet another relational database?

    3. Re:This project by Karamchand · · Score: 3, Informative

      Firebird is supported by PHP quite well. Just take a look at the InterBase Function Reference for more information.
      I guess Perl has a module for it as well...

    4. Re:This project by Just+Some+Guy · · Score: 5, Informative
      Its main claim is that it sucks less than Interbase, so if you have to support a horrid Interbase installation, then upgrading to Firebird would probably be a good idea.

      On the other hand, I hated having to administer that hell-pit of a server so badly that I wrote a migration program to transfer entire databases from Firebird to PostgreSQL. I can't describe how happy I was to switch a fairly large online store's backend to a modern platform.

      --
      Dewey, what part of this looks like authorities should be involved?
    5. Re:This project by AndroidCat · · Score: 3, Informative

      Since Interbase was around long before MySQL and PostgreSQL, why did anyone bother making them? Besides, we need enough DBs to match the number of editors available.

      --
      One line blog. I hear that they're called Twitters now.
    6. Re:This project by bwt · · Score: 4, Informative

      Why do we ask companies to GPL their aging products and then ask if anyone cares?

      This RDBMS is a viable peer to PostgreSQL. It has many features that MySQL does not have.

      Just the other day, there was a good article about this database.

    7. Re:This project by Zaiff+Urgulbunger · · Score: 2, Interesting

      Not disagreeing at all, but could you expand on what was bad about Interbase vs. Postgre?

    8. Re:This project by Just+Some+Guy · · Score: 4, Informative

      Follow the first "Interbase" link in my post to read the explanation I'd written earlier. Some of the problems might've been fixed by now, but it boils down to this: PostgreSQL is widely used, fast, supports the same features, and has major commercial backing. Firebird's main strength is that is used to be Interbase and is a good thing for people with legacy applications built around that system. It's almost like a comparison of Python and COBOL - both are Turing complete, sure, but I'd hate to do new development on the latter unless I worked in a shop that depended on it.

      --
      Dewey, what part of this looks like authorities should be involved?
    9. Re:This project by nelsonal · · Score: 4, Funny

      You only need a single DBMS and it will be included in the next point release of emacs.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    10. Re:This project by arf_barf · · Score: 3, Insightful

      Have you considered that what's good for you might not be good for everybody else? I for one, take the ease of administration and deployment of Firebird any day over something as horrendous as Postgre in that department.

      Heck, in my small MS centric world there isn't even a way to distribute Postgre with my application. The only good thing about the Postgre from my point of view is the BSD license and that's about it....

    11. Re:This project by Ludoo · · Score: 2, Informative

      hmmm your observations on firebird are mostly FUD, and should be modded down:

      1 - if you change your dir layout, a symlink pointing to the new db locations is enough (helloooo, stop thinking in terms of apps, learn some basic sysadmin)

      2 - Firebird has a new isql with readline capabilities, and there are plenty of good frontends (ibexpert is one) for interbase, isql is a tool of last resort

      3 - same as no. 2, but I wonder which IB you were using, SuperServer or Classic? you should specify that

      4 - YMMV, I never experienced any corruption and I suspect it's a hardware issue; there's a tool (gfix) to fix the db anyway which usualy works, and hot backups are so easy (gbak -B -V dbfile.gdb bakfile.gbk) you should do them often

      5 - you can extract metadata, I'm not sure about SQL statements, but as you say it's not difficult todo it by hand; good clients (eg IBExpert) have a "data pump" to do exactly that

      IB is stable, has a small footprint and lots of goodies only found in major league RDBMSs.

    12. Re:This project by Ludoo · · Score: 1

      OMG, did you say that comparing Interbase and Postgresql is like comparing Python and Cobol? in a message modded +4??????

      I'm curious to know how you use Python (or COBOL), LOL

    13. Re:This project by Just+Some+Guy · · Score: 1
      1 - Gee, do you think we might've tried that?

      2 - I'm not surprised. Of course, I wrote that three years ago.

      3 - We were using SuperServer.

      4 - gfix and gbak segfaulted every time we tried to run them, even after moving the whole mess onto a new server.

      5 - See also my program that I mentioned in the post you replied to. :-)

      YMMV, of course, but on our server IB was big, slow, and crashy, and supported features that the shop wasn't using at that time. It was a complete loss for us.

      --
      Dewey, what part of this looks like authorities should be involved?
    14. Re:This project by anti-trojan · · Score: 1

      Just nitpicking, but Interbase wasn't open source when they started being written.

    15. Re:This project by justins · · Score: 1
      PostgreSQL is widely used, fast, supports the same features, and has major commercial backing.

      You could say the same thing about MaxDB (aka SAP DB) as well, and the "commercial backing" part would actually be true. :)

      http://www.mysql.com/products/maxdb/index.html
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    16. Re:This project by rembo · · Score: 1

      Firebird (and Interbase) are also supported in PEAR which enables you to write database portable code to a large extent. I use PEAR DB myself.

    17. Re:This project by rembo · · Score: 1

      I forgot to mention, there is a very powerfull webbased administration tool available for firebird. It's called ibwebadmin.

    18. Re:This project by Sxooter · · Score: 1

      www.pgsql.com
      www.commandprompt.com
      www.redhat.c om

      Postgresql has REAL commercial support, and it isn't being sold by one company trying to extort money out of you for using their product commercially.
      It's supported by several different companies, and if you don't find one fits your needs, you can pick another.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    19. Re:This project by ceeam · · Score: 1

      >Just kind of curious if anyone would care at all if
      >there hadn't been the big stink with the name
      >conflicts.

      Yes. Many people would care ("People who know...")

      >I mean, has anyone used this database?

      Sure. Or do you believe that all people are programming in C++ and use Oracle? ;)

      >Is it really of any note that v1.5 is out?

      Well, considering that RC's were _very_ stable, probably not. Nice to know though.

    20. Re:This project by aliens · · Score: 1

      You're right, people obviously care. But I meant my question to be more along the lines of, if there wasn't the conflict with Mozilla, would this be frontpage news on slashdot rather than a newspost on freshmeat?

      --
      -- taking over the world, we are.
    21. Re:This project by justins · · Score: 1

      Oh yes, commandprompt.com. I don't know how I could have overlooked THEM!

      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    22. Re:This project by Sxooter · · Score: 1

      Yeah, they're so unimportant that they provide the replication code that afilias uses to run .org and .info on.

      and plperl, plphp, and a half a dozen other useful parts of postgresql.

      Yep, never heard of them before.

      Just because your outlook is limited, don't expect everyone else's to be.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    23. Re:This project by justins · · Score: 1

      None of which makes them even remotely important in the context of the discussion, which is "commercial backing" for databases. The only company you mentioned which matters for that is Redhat. And it appears to be a teeny-tiny part of redhat's business.

      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    24. Re:This project by Sxooter · · Score: 1

      Actually, it's VITALLY important. It proves that the different companies that support postgresql are more than just houses of funky consultants with little or no experience. These support companies actively write both free and commercial add ons to the database, and therefore are guaranteed to have in house talent to meet your needs should you have a really difficult problem to work out.

      Here are a few more companies that provide both products and support for postgresql.

      How many companies are providing support for MySQL besides MySQL? How much choice do you have, and how good is it?

      http://www.linuxlabs.com/welcome.html -> Clustered Postgresql solutions and postgresql support contracts
      http://www.refractions.net/ -> PostGIS indexing and postgresql support contracts
      http://www.dbexperts.net/ -> clustering and postgresql support contracts
      www.nusphere.com -> IDE for PHP/Postgresql, Native windows port of Postgresql, support for their native windows port.

      Note that all of these, including those in my grandparent post, provide both full postgresql support in ADDITION to those products they provide and the support for said products.

      Look, you were WRONG. Absolutely, and unequivocably wrong. Postgresql has real companies providing real support. It runs real databases where data integrity and 24/7 operation are critical to the business, and it does so quite well, and one of the reasons it does so is that it is very well supported, both by the community and by commercial companies with a stake in seeing it succeed.

      MySQL is a single source product. One company does virtually all the development, and all the support. And if they aren't doing what you want, you're options are significantly more limited than they are with Postgresql.

      Those are facts. Your original post was a lie of ignorance. Your further defending it just makes you look so much more desperate.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    25. Re:This project by justins · · Score: 1
      Look, you were WRONG. Absolutely, and unequivocably wrong.

      Ooooh. You go girl!
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
    26. Re:This project by Sxooter · · Score: 1

      Wow, you must've been the most feared one on your high school debate team. Never in the annals of history has one so fomiddable in the artform of debate has one existed as great and unbeatable as justins.

      In a pig's eye. You're not even a very good troll.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
  3. Firebird for web sites by chrysalis · · Score: 3, Interesting

    How does it compare to MySQL for web sites, that typically makes a lot of short connections to the same database?

    --
    {{.sig}}
    1. Re:Firebird for web sites by Anonymous Coward · · Score: 4, Funny

      Firebird works really good for Web sites.
      Much better than Internet Explorer.

    2. Re:Firebird for web sites by Anonymous Coward · · Score: 1, Informative

      Not sure, but I'll say that I will investigate it and give it a try for CGI/Web stuff because of the countless headaches one encounters with mysql.
      I always thought mysql was a fairly 'lite' db compared say to Oracles tools, but in practice its given me nothing but trouble. I never heard of interbase before today, databases are not my thing, but I will give it a try. The list of people who put their trust in this software is also impressive.

    3. Re:Firebird for web sites by slycer · · Score: 4, Informative

      I used interbase at a previous shop (had to, the "fearless leader" was a borland guy through and through).

      I can say that it seemed to handle fine, the server never crashed, there was never a corruption etc - and this was for fairly large databases as well (million+ records etc)..

      Firebird I'm sure improves even further on it, the only problem I had with it was it's horrid horrid gui interface(s).

    4. Re:Firebird for web sites by aldoman · · Score: 1

      What have you been doing with mySQL? There is nothing super-complex that really belongs with mySQL, even if 'mySQL AB' tells you so. mySQL is perfect for dynamic websites, but not much else.

    5. Re:Firebird for web sites by jgbustos · · Score: 3, Informative

      Basically, the main difference is that Firebird is a fully transactional database server, whereas MySQL is not.

      Rollback and commit.

    6. Re:Firebird for web sites by Anonymous Coward · · Score: 0

      You haven't used mysql in a LONG time, have you?

    7. Re:Firebird for web sites by joeykiller · · Score: 3, Insightful

      I've not tried Firebird since the pre-1.0 versions, but I have to say that it was nice to use. What was most interesting for me was the availability of subselects, referential integrity between tables and the stored procedures. All of the stuff that MySQL lacked (and still lacks in usable form).

      Firebird was extremely easy to set up and configure (= almost no configuration). So that couldn't have been easier.

      But then there was the speed issue: At the time Firebird was not a speed daemon. The one thing that bugged me most, though, was that when connecting to the database -- even if you did so from a remote host -- you had to know the physical location of the database file on the server!

      It's strange what turns you off, and this peculiarity annoyed me enough to start investigating other options instead. I'm now using Postgresql when I need the more advanced SQL features.

    8. Re:Firebird for web sites by Zaiff+Urgulbunger · · Score: 1

      You're getting mixed up with that Borland Interfox thing arn't you?!

    9. Re:Firebird for web sites by fm6 · · Score: 4, Informative

      That's one difference. But query optimization is also a big deal. It's not obvious from simple queries, but MySQL takes a big performance hit if you do anything that involves relations between tables. That's why Slashdot went to indexing posts using a single field, instead of referencing the parent story every time. (It also has the effect of discouraging "first posts" since there's no longer a post #1. But Taco doesn't actually care about that!) I find it hard to take seriously any database that doesn't optimize queries.

    10. Re:Firebird for web sites by Anonymous Coward · · Score: 0

      "The one thing that bugged me most, though, was that when connecting to the database -- even if you did so from a remote host -- you had to know the physical location of the database file on the server!"

      Now you don't need to do that. You can set up a list of aliases on the server and just use the database name without any path. (At last!)

    11. Re:Firebird for web sites by Anonymous Coward · · Score: 0

      MySQL InnoDB has supported rollback and commit for a long time now.

    12. Re:Firebird for web sites by Anonymous Coward · · Score: 0

      You mean FoxPro, surely ?

    13. Re:Firebird for web sites by Anonymous Coward · · Score: 0

      No, I think he means Foxpage. It's Microsoft's web programming app.

    14. Re:Firebird for web sites by Anonymous Coward · · Score: 0

      So what happens if I ALTER TABLE and then ROLLBACK in MySQL?

    15. Re:Firebird for web sites by Zaiff+Urgulbunger · · Score: 1

      Nope, that'd be FuxPage! Well it does doesn't it?! :D

    16. Re:Firebird for web sites by F1re · · Score: 3, Informative

      You don't need to know the physical location anymore. Version 1.5 has aliases.

      --
      ...there is no sig...
    17. Re:Firebird for web sites by chrysalis · · Score: 1

      MySQL has transactions for 5 years.
      I've never used MyISAM.

      --
      {{.sig}}
    18. Re:Firebird for web sites by rembo · · Score: 1

      You can connect using a persistent connection instead of a short one. with the php function ibase_pconnect. That way your connection will be reused. The database performs quite well in my experience.

    19. Re:Firebird for web sites by Sxooter · · Score: 1

      The same thing as Oracle 9i, it errors out because DDL isn't transactable in very many databases.

      The only non-transactable DDL / DML command is create / drop database... :-)

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    20. Re:Firebird for web sites by fferreres · · Score: 1

      It does not take a big performance hit. Maybe you are talking about a corner case, but you have a high degree of query optimizations to do with MySQL. Yes, there are some things that you should be aware. For example, if you used an int(11) field in one table, and an int(12) in a second table, then a join would not use the queries. In that case you should make the int(11) an int(12). There are many things like that. The EXPLAIN in MySQL helped bring 11s queries to 0.001s queries in little time. You also learn to think correctly when doing queries, avoiding stupid queries that _seem_ right.

      --
      unfinished: (adj.)
    21. Re:Firebird for web sites by shadowmas · · Score: 1

      its been some time since i used this but i think firebird allows simple alter statements to be transactable. i remember it happend to me once by accidednt. not sure though maybe i should check it out later..

    22. Re:Firebird for web sites by fm6 · · Score: 1

      Perhaps I spoke beyond my expertise. But there is a relatively experienced MySQL programmer who says that multi-field primary keys and indexes for string fields are expensive to use in MySQL.

    23. Re:Firebird for web sites by ceeam · · Score: 1

      Connection times are _vastly_ improved now (well, they are virtually instantaneous now, much like w/ MySQL). About interface: try IBExpert - it kicks ass compared with other vendors' included tools (Windows only though).

    24. Re:Firebird for web sites by Sxooter · · Score: 1

      I should clarify, that the statement:

      The only non-transactable DDL / DML command is create / drop database... :-)

      was in reference to Postgresql.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    25. Re:Firebird for web sites by Arioch_BDV · · Score: 1

      With Firbird or Yaffil you can just open read-only transaction and never close it.
      Indeed one of suggested mode it bi-connection, when each applications holds 2 connections: one for transaction looooong read-only with 'read-commited', and one for short transactions, changing data.

    26. Re:Firebird for web sites by fferreres · · Score: 1

      Could be...but still indexes in mysql make the queries really fast. The question you have to ask with using mysql is: "do I do a large of INSERTs or UPDATEs, and few SELECTs", in that case, I believe MySQL is not your best solution.

      --
      unfinished: (adj.)
    27. Re:Firebird for web sites by fm6 · · Score: 1

      In other words, MySQL is an ISAM engine with a pseudo-relational front end.

  4. Firebird(tm) and why I just don't care by SeanTobin · · Score: 0, Flamebait

    You know, I really don't have anything against the firebird(tm) db people. I'm sure they are all fine coders and the DB is probably fairly decent. Personaly, I'm not leaving mysql anytime soon but that is beside the point.

    I'm not looking at thier web page. I'm not considering Firebird(tm) for any projects. I'm not recommending it to other people. I don't even really care about any new features in yet another relational database.

    Why? Why would anyone go out of thier way to not learn about a (free?) new database release? My reasons are simple. I don't like the way they handled the Mozilla/Firebird naming issue. Does that have anything at all to do with the quality of thier products? I doubt it. Should I be so shallow so as to pre-judge an entire company and thier products by the way they handle thier PR? Probably not... but I'm still not sending SCO $699.

    --
    Karma: SELECT `karma` FROM `users` WHERE `userid`=138474;
    1. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Please explain, what exactly didn't you like about how they handled the naming conflict? You didn't like that they hadn't just given up their name?

    2. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      +1, word.

    3. Re:Firebird(tm) and why I just don't care by finkployd · · Score: 5, Interesting

      Specifically what did they do wrong in your eyes? When Mozilla takes an existing project's name are they just supposed to accept it and change their name? That doesn't sound very fair.

      Finkployd

    4. Re:Firebird(tm) and why I just don't care by MyHair · · Score: 4, Funny

      Firebird is SQL, not relational.

      Yip yip yip! Ow! I sprained by brain!

    5. Re:Firebird(tm) and why I just don't care by cubic6 · · Score: 5, Insightful
      Firebird is SQL, not relational.
      There might be a reason why you're a DBA looking for a job. SQL is a query language, relational is a database design paradigm. As it says all over their homepage, Firebird is a relational database that uses SQL.
      --
      Karma: Contrapositive
    6. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Talk about cutting off your nose to spite your face.

    7. Re:Firebird(tm) and why I just don't care by {Hecubus} · · Score: 1

      Why can't they both just be called Firebird?

      People who actually use a relational database should be smart enough to be able to tell the difference between Firebird the browser and Firebird the database.

      Its not like they are competing products or something.

      --
      Unix is mysterious, and ancient, and strong. It's made of cast iron and the bones of heroic programmers of old -
    8. Re:Firebird(tm) and why I just don't care by SeanTobin · · Score: 2, Insightful
      Please explain, what exactly didn't you like about how they handled the naming conflict? You didn't like that they hadn't just given up their name?
      No, I do not think they should have given up thier name. They are entitled to use it as much as Pontiac is. From my understanding of the situation, the Phoenix code name was changed to Firebird, and then to Firefox for thier final brand. They were code names for projects similar to Merced or Coppermine. The final name was always going to be changed to something once the release came.

      Also, from what I remember from the incident I had a very bad impression of the Firebird project. I no longer have any links but what I remember now about it (granted it may be totaly different from what actually happened.. but this is how I view it right now) was the Firebird people attacking Mozilla and writing a very forcefull letter demanding the name change. I believe that a less agressive approach would have produced the same results, and a more positive image for the company.

      As far as the relational database vs SQL, I don't know *anything* about the firebird project. All I know is the title here on /. about the 'Firebird relational database.' I always believed the database was relationaly designed and interfaced via SQL but what do I know..

      I've already generated a ton of negative comments about my post, but remember this is just my opinion. It's the opinion of a linux sysadmin/perl monk/mysql user who is probably in thier target market. I'm just letting them know why I just don't care.
      --
      Karma: SELECT `karma` FROM `users` WHERE `userid`=138474;
    9. Re:Firebird(tm) and why I just don't care by finkployd · · Score: 1

      Personally I don't care except that it sets a bad precedent. In this particular case few people really would care BUT I don't like the idea that it is OK to do this at all. You know if it were the other wat around Mozilla would have gone after them.

      Finkployd

    10. Re:Firebird(tm) and why I just don't care by zangdesign · · Score: 1

      Why not? They were there before.

      One's a database product. The other's a browser. Kinda hard to confuse the two, I should think. They don't compete in the same arena, unless you consider the entire open source/free software movement their arena.

      In the end, it probably didn't really matter. Firebird is still obscure compared to some of the other longstanding offerings, and the name change didn't hurt the Mozilla team any, although I do wish they would stop naming each release, and just stick to one damn name.

      --
      To celebrate the occasion of my 1000th post, I will post no more forever on Slashdot. Goodbye.
    11. Re:Firebird(tm) and why I just don't care by lonenut · · Score: 1

      I think the problem for many people is the HUGE stink the FBDB folks made of the whole thing. I didn't hear Pontiac complaining when the Firebird DB people stole the name from them (or the indigenous peoples of the Americas where Pontiac stole it).
      I mean really, the odds that someone would confuse 'Firebird the browser' with 'Firebird the database' are about as big as confusing 'Firebird the car' (or deity) with 'Firebird the database'.

    12. Re:Firebird(tm) and why I just don't care by MyHair · · Score: 1

      Okay, I guess I could post a real post instead of attempted funny one-liners.

      Firebird is SQL, not relational.

      Actually, the title of the Slashdot article and the linked Firebird project page both proclaim that it is relational.

      And I could be wrong, but I thought SQL is specifically for relational databases. I suppose you could use a simple SELECT statement on a standalone table, but I would think most SQL breaks without a relational database underneath.

      I agree with your rebuttal of the grandparent post, though. What's wrong with another open source project? Especially one with dedicated people? I don't know if Firebird is useful to me as a database, but it doesn't take long for me to infer that there is a dedicated development team and community behind it, and I'm not about to go trying to convince them to support PostgreSQL MySQL or any other project.

      And I can't understand why anyone would hold the naming issue against them. Maybe it was just a successful troll. Does the grandparent poster refuse to use Phoenix products, too?

    13. Re:Firebird(tm) and why I just don't care by finkployd · · Score: 3, Insightful

      I agree to an extent (the Pontiac example is a little extreme though). However, if it were the other way around I would bet good money that Mozilla would have gone after them. And if nothing else, it sets a bad precedence. This kind of namespace collision should be avoided in the OSS community where people are confused about what programs to use as it is.

      Finkployd

    14. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Igor Stravinsky kicks the asses of both the Mozilla developers and the Firebird database developers.

      Why? 7/4 time in the finale of the Firebird Suite! Now there's some musical jujitsu in action. The name was used far prior to either computer program.

      All of you that haven't the slightest idea what I'm talking about need to get some culture. :P

    15. Re:Firebird(tm) and why I just don't care by __past__ · · Score: 1
      He is technically correct. SQL as a language, and the database management systems that use it, are not strictly implementations of relational algebra/calculus as CS defines it. Simple example: SQL's NULL doesn't make sense in the CS relational model.

      In practice, it doesn't matter. The term "relational database" used to describe a real piece of software does not neccessarily imply strict conformance to the relational model as defined in CS textbooks. It is just another example of the same word used to refer to slightly different concepts in different contexts.

      It is a little like saying that Objective Caml is not a functional programming language, because it allows side effects. In one sense, it is true, but not in the sense people care about.

    16. Re:Firebird(tm) and why I just don't care by FattMattP · · Score: 1
      Specifically what did they do wrong in your eyes?
      Well they did encourage their users to crapflood the Mozillazine forums. Even though I feel that Mozilla was in the wrong, the FirebirdDB people handled things improperly.
      --
      Prevent email address forgery. Publish SPF records for y
    17. Re:Firebird(tm) and why I just don't care by bwt · · Score: 2, Insightful

      I don't like the way they handled the Mozilla/Firebird naming issue.

      If Mozilla had called their browser "Linux" or "Apache" or "Python" would you have taken the same position? Or do you feel it is only an issue if they choose the same name as a project you've personally worked with.

      Mozilla was clearly in the wrong there, but they did the responsible thing and renamed their project to Firefox and even came up with a cool logo to match their new name. That issue is resolved to everyone's satisfaction, so why would you keep bringing it up after it is fixed? It's time to move on.

    18. Re:Firebird(tm) and why I just don't care by finkployd · · Score: 1

      Yeah, I'll give you that. It was handled poorly on both ends. Firebird should have been a little less aggressive, Mozilla should never have picked that name to begin with.

      Finkployd

    19. Re:Firebird(tm) and why I just don't care by GarfBond · · Score: 2, Interesting

      How about, why couldn't they just let things go?

      Trademark law allows for things to have similar names if they're in different fields. Although both are in software, *nobody* who is looking for Firebird the database is going to confuse it with Firebird the browser, especially when both show up in the top 10 of google for 'firebird'. If anything, it goes the other way around.

      In fact, out of this whole thing, the Firebird DB people probably benefited the most out of the whole charade. They got a bunch of free publicity, and as evidenced here, there's a crap load of people who now know what it is and would otherwise have no reason to.

      And their conduct throughout the ordeal was less than sportsmanlike. True, MozillaFoundation probably should've done a little better checking on it, but most likely in their eyes they came to the same conclusion we did: confusion between the 2 projects wasn't likely. However, this didn't stop the FirebirdDB people from being near harrassing. Their first 'call to action' was to essentially mailbomb anyone and everyone Mozilla related (http://www.mozillazine.org/talkback.html?article= 3115). Perhaps if they had been a little more understanding and realized that the uproar about this took Mozilla by surprise as much as it did for them, maybe there wouldn't be some ill-will.

      At the time, Mozilla.org was part of AOL. AOL's a big company. Big companies move slowly. The issue was going to be resolved (partially with the name Mozilla Firebird instead of just Firebird) anyway.

      In the end, changing to Firefox was definitely the right thing to do. No confusion with anybody else, no wondering about what GM thinks about the name, brand spanking new logo, and clear skies until 1.0 :)

    20. Re:Firebird(tm) and why I just don't care by finkployd · · Score: 0

      Pfft, Pink Floyd's Money is entirely in 7/4 time (well ok, except for the guitar solo, I think it switched to 4/4 for that).

      Finkployd

    21. Re:Firebird(tm) and why I just don't care by uradu · · Score: 1

      Firebird is cool, but Le Sacre Du Printemps is better. In that musically purely objective way, of course ;-) If you can start an audience riot with a piece of ORCHESTRAL music, you've GOT to be one cool dude!

    22. Re:Firebird(tm) and why I just don't care by GarfBond · · Score: 1

      Just to clarify something:

      I understand that for the DB people it hurts to have name confusion with a much more visible project with formerly large backers. I personally don't have any ill will to them ("Mozilla Firebird" generally solved most of the confusion a long time ago, and now it's a done deal). But, in the heat of the moment, their conduct could've been a little better.

    23. Re:Firebird(tm) and why I just don't care by cetan · · Score: 2, Insightful

      How about the fact that their first response to the browser name was to mail bomb everyone at Mozilla?

      Yeah, I guess that's how adults act....

      --
      In Soviet Russia...michael would be rotting in Siberia!
    24. Re:Firebird(tm) and why I just don't care by SeanTobin · · Score: 1

      No, I do not think they should have given up thier name. They are entitled to use it as much as Pontiac is. From my understanding of the situation, the Phoenix code name was changed to Firebird, and then to Firefox for thier final brand. They were code names for projects similar to Merced or Coppermine. The final name was always going to be changed to something once the release came.

      Also, from what I remember from the incident I had a very bad impression of the Firebird project. I no longer have any links but what I remember now about it (granted it may be totaly different from what actually happened.. but this is how I view it right now) was the Firebird people attacking Mozilla and writing a very forcefull letter demanding the name change. I believe that a less agressive approach would have produced the same results, and a more positive image for the company.

      As far as the relational database vs SQL, I don't know *anything* about the firebird project. All I know is the title here on /. about the 'Firebird relational database.' I always believed the database was relationaly designed and interfaced via SQL but what do I know..

      I've already generated a ton of negative comments about my post, but remember this is just my opinion. It's the opinion of a linux sysadmin/perl monk/mysql user who is probably in thier target market. I'm just letting them know why I just don't care.

      Some other users have posted some interesting information regarding the 'stink' that the FBDB people did, including mailbombing the mozilla developers. Any project that resorts to that level of action has to do a heck of a lot to not be considered crap in my eyes.

      Also, for the record I don't work for/on Mozilla/Firebird/Firefox. I have submitted several bug reports regarding mozilla and I use Mozilla as my primary browser. I have played around with firefox and I do like it. I have never heard of firebird before thier actions, and I have never used thier products ever.

      --
      Karma: SELECT `karma` FROM `users` WHERE `userid`=138474;
    25. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 1, Interesting

      It sure confused enough people that I spoke to. They'd ask what database I use, and when I said Firebird they'd say something like 'Oh, I thought that was a browser?', or 'I didn't know they made databases as well.'

      I for one was pleased when Firefox received it's latest name, although it's going to take a while before people stop being confused since most people now think that Firebird is a browser.

    26. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Well they did encourage their users to crapflood the Mozillazine forums

      You leave out the reason WHY they went to Mozillazine.

      Mozilla.org basically told them "Hey, We're AOL. We have lots of lawyers. You gotta problem with our name? Sue us.", and then ended communication.

      Furthermore, when you install "Phoenix" (etc), it comes with bookmarks implying Mozillazine is the official forums, which is why the FirebirdDB people went their to register their complaints.

    27. Re:Firebird(tm) and why I just don't care by kfg · · Score: 1

      They can say anything they want in their advertising material. SQL is an alpha test implimentation of the relational database model that IBM released to the public against Codd's (the inventor of the relational model) wishes.

      It does not actually impliment the relational model, and is thus not really a relational database, merely what the marketers choose to call a relational database so that they might sell them as such.

      When SQL products further confound the issue by tying the query language to the physical data storage system they also remove any claim that it is merely a logical query language.

      One cannot make proper use of SQL without knowing what the relational model is, because then one cannot intelligently compose workarounds for the flaws and limitations of a particular SQL product.

      If parent poster is a DBA looking for a job because he understands the difference between the relational model and SQL it is because the people who are doing the hiring do not know their business, especially if they are DBAs themselves.

      KFG

    28. Re:Firebird(tm) and why I just don't care by FattMattP · · Score: 1

      Why they went there doesn't change the fact that they were encouraging abuse not constructive discourse.

      --
      Prevent email address forgery. Publish SPF records for y
    29. Re:Firebird(tm) and why I just don't care by Zaiff+Urgulbunger · · Score: 2, Informative

      Well maybe they don't like *your* attitude! You, sitting there, picking the fluff out of your fat ass and making condescending statements like the above!! ;)

      These are commited people, spending their own time on a quality database that is available to everyone. You don't have to use it, but don't bleat about just 'cos somehow they've upset you because of a product naming arguement that in all likelyhood you are probably not a party to anyway!

      I mean, regardless of if you think Firebird-SQL, Mozilla or both were in the wrong over the naming debacle, it is now resolved, and the vast majority here are fortunate to have the opportunity to use *BOTH* for free without having to do a thing.

      So climb down off the moral high-ground, and say something constructive or nothing at all!

    30. Re:Firebird(tm) and why I just don't care by ManxStef · · Score: 3, Informative

      Hardly. They did publish a list of people the express dissatisfaction to, which in hindsight was an incredibly stupid mistake, but the wording wasn't anywhere near the "spam/flame all these people" you make out. Arguably they didn't expect many people to respond as the Firebird community (much like the Delphi community that uses Firebird) is fairly small, tight-knit and rational - so they didn't expect people to behave childishly by flooding the mailboxes of the Mozilla team.

      However, because it made "good news" to have an open-source battle (or to create one, which the media is sometimes guilty of) it gained publicity fast and was picked up by people on both sides, including those who'd probably used neither product who thought it'd be good to fan the flames and as a result things escalated wildly - to the extent that some stupid Firebird fanboys mailbombed the Moz devteam while on the other hand some idiotic Mozilla zealots found an SSL bug in the Firebird website and deleted everything...

      So to say that only the "FirebirdDB people" handled things improperly is a pretty wide-sweeping generalisation that, if you stepped back a bit and checked out the facts, might reveal a slight subconscious leaning to Mozilla 'cause you like their browser? I've used both products and saw plenty of mistakes made on *both sides*...

      FYI I did a a writeup of events last time around.

    31. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Most people would consider "abuse" to be things like posting Goatse pics or scriptbombing. The posts from the FirebirdDB people were generally polite and rational. Besides, 90% of the "crapflood" was Mozillazine regulars flaming each other, not FirebirdDB people.

      Conclusion: the supposed "Mozillazine Crapflood" is just an excuse so that one side could feel morally vindicated in some way. Nothing really happened.

    32. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Me, I decided not to pay any attention to their product. They mailbombed another project to get their way. That's all I know about 'em. Technical issues/merits don't even rise high enough in this case. So, their product gets excluded from my thoughts. Since they are a small fish in a big pond, I'm not hurt a bit. In fact, I might get some benefit if excluding them helps gets rid of a group which tries to be destructive when settling disputes. So technical opinions aside, the name fiasco showed other concerns. I'm just don't see a need for a group that will lash out like that.

    33. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      googling for firebird minus any reference of mozilla or database still results in 803,000 results.

      look, if you're going to pick a name as common as firebird you're going to have to accept the possibility of another software product using the same name. a web browser is not in the same domain as a database. it's that simple. mozilla clearly was NOT in the wrong here.

      the responsible thing was for mozilla to do was to research the name before using it, which they had done (with aol's lawyers i believe). by renaming the browser again to firefox was simply them being extra nice to the firebird-db team. do not confuse mozilla being nice with them being wrong, because mozilla could have easily just kept the firebird name. the firebird-db team would have probably sued, but nothing would have changed.

      and don't feel sorry for the firebird-db team. feel sorry for the software programs that existed before they came around. did it bother the firebird-db team that there were other programs around that had already laid claim to the name, "firebird"? obviously not. back then, they were the big open source project based on Borland's Interbase. they were going to turn heads. i guess they assumed that if any software decided to used "firebird," it would either be too small to matter or they could just bulldozed them over.

      very hypocritical of them IMHO.

    34. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      you're probably being modded down by firebird-db supporters. i agree with you that the firebird-db team acted unprofessinally, but i'm not foolish enough to post those views other than as AC. my view of the events are pretty much inline with that what you've probably remember. though i would still consider using their db based on the its technical merits.

    35. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Personally I don't care except that it sets a bad precedent. In this particular case few people really would care BUT I don't like the idea that it is OK to do this at all. You know if it were the other wat around Mozilla would have gone after them.

      like the precedent the firebird-db team set when they first named their project "firebird." weren't there a whole lot of programs that already used the "firebird" name when the db team came around? did that stop them. obviously not.

      here's another comment i posted that kinda sums up how i feel about this whole issue: here. i'm posting AC simply because i know how unpopular this position is on slashdot. feel free to rebuff my comment though.

    36. Re:Firebird(tm) and why I just don't care by cubic6 · · Score: 1

      Ok, I get that he's technically correct according to Codd. However, by his definitions, there isn't a database I've seen that fully implements the relational model. If you have an example of a mature, widely database system that qualifies as a relational database system, I'll stop calling Firebird and Oracle and DB2 relational. Until then, I'll let the marketers call their products whatever they want, because they've produced a useful product that's used by millions. Codd's research is useful, but the word relational has changed in meaning since his time.

      --
      Karma: Contrapositive
    37. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      In order of appearance:

      Firebird BBS
      FirebirdSQL
      Mozilla Firebird

      I think the FirebirdSQL team is being slightly hypocritical here. Actually if memory serves me correctly, there are suppose to be quite a few number of software projects named "Firebird" that existed before the database project was started.

    38. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      That doesn't make the FirebirdSQL team any less immature. Whether you believe Mozilla was right or wrong, you have to agree that at least Mozilla acted professionally.

    39. Re:Firebird(tm) and why I just don't care by kfg · · Score: 1

      A ballpeen hammer is a very useful tool for opening a can of paint, if that's all you have.

      The marketers labeling it as a canopener doesn't make it one, however.

      Relational Database has as precise a technical defintion as the do the laws of thermodynamics. If popular usage of the word thermodynamics, or marketing manipulation of the word, differs from the definition it isn't because the definition has changed. It is because those who misuse it are ignorant of what it means.

      I'm sorry, I have to run now. The CD in my cupholder needs changing.

      KFG

    40. Re:Firebird(tm) and why I just don't care by Zaiff+Urgulbunger · · Score: 1

      Well first up, I really don't know who was to "blame" -- I only know what I've read, and really it depends on who's writting! Mozilla used a name that the Firebird-SQL people were already using so they complained... it looks like they handled that badly, but the way the story gets re-told is that they orchastrated an email DoS attack, which I don't personally believe was the intent. Just some Firebird-SQL supportors took things the wrong way and wound up the Mozilla people.

      Anyway, regardless, the issue has been resolved. The Mozilla folks now have a new name and a cool new logo to boot! The only thing that remains is people trolling when ever Firebird-SQL is mentioned.

      Whether you believe Mozilla was right or wrong, you have to agree that at least Mozilla acted professionally.
      I don't think anyone disputes this. It was all an unfortunate situation. But its all sorted now!!

    41. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      their posts were def were not polite.

    42. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      heh, agreed. one of the most insightful things i've read all day.

    43. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Actually, I do sort of remember the FirebirdSQL group bombing MozillaZine with mass amounts of posts. It was kind of ridiculous. I think the old main forum was removed and replaced shortly after the FirebirdSQL people calmed down, but you can probably still see some of the posts from the MozillaZine news topic forum if you looked.

    44. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Mozilla.org basically told them "Hey, We're AOL. We have lots of lawyers. You gotta problem with our name? Sue us.", and then ended communication.

      I thought it was basically more like, "Why on earth would you have a problem if we used 'Firebird'? You're doing a database. We're doing a web browser. Completely different. And oh yeah: AOL's lawyers have already spent months researching this for us and have said that it was O.K. for us to use the name."

      I think you stretched the part about AOL a bit. Mozilla was most likely right in this case, but they were nice enough to rename the browser again just to minimize conflict.

    45. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      I thought AOL's lawyers had spent several months researching a legal replacement name for Phoenix before finally deciding on "Firebird." I would have to imagine that they knew what they were talking about when making a recommendation to Mozilla. Furthermore from what I understand there were previous occurances of software that had been named "Firebird" before the FirebirdDB project was launched.

    46. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Couldn't the same be said of the FirebirdDB project when it was first formed? Even though there were previous occurrences of software titled "Firebird," they said "Hey, We're Borland. We have lots of lawyers. You gotta problem with our name? Sue us."

    47. Re:Firebird(tm) and why I just don't care by rsheridan6 · · Score: 1

      Anyone who's techie enough to give a shit about a relational database would not be confused by a web browser with the same name. They would be referred to in totally different contexts. So the Firebird people gave a lot of crap to the Mozilla people, and made us go through another confusing name change for no good reason.

      --
      Don't drop the soap, Tommy!
    48. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Firebird is SQL, not relational.

      What the fuck?!

      Uh.. SQL is an interfacing language for RDBMSes. Saying "it's SQL, not relational" is kind of like saying "it's a vehical, not a van".

    49. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      And there was a massive number of posts on Slashdot as well -- and almost none of them were from "FirebirdSQL people".

      Face it, the Mozilla decision was massively unpopular and attracted a lot of interest. 99% if the people making noise were not FirebirdDB developers or users.

    50. Re:Firebird(tm) and why I just don't care by leandrod · · Score: 1
      > There might be a reason why you're a DBA looking for a job.

      Perhaps because people who have been trained instead of educated don't want to hire people who have a more solid knowledge than themselves?

      Seriously, thanks, I've got a job now. Just forgot to update my .sig... will do RSN.

      > SQL is a query language, relational is a database design paradigm.

      Stop short that paradigm crap. It is a theory, not a (ill-defined) paradigm.

      Now, how would you feel if you had had a Math teacher who had taught you his own invention of a nifty algebra notation that didn't conform to the applicable Mathematical theory? Cheated, furious, or what?

      > Firebird is a relational database that uses SQL.

      The Relational Model pertains not to the physical level (DBMS engines) but to the interaction level (data languages). SQL is not relational. Therefore, a SQL DBMS is not relational, no matter if its engine is capable of supporting a relational language too.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    51. Re:Firebird(tm) and why I just don't care by leandrod · · Score: 1
      > the title of the Slashdot article and the linked Firebird project page both proclaim that it is relational.

      That was my point, that they are in error.

      That such a fundamental error is propagated even by DBMS implementors speaks truckloads about levels of knowledge in the industry.

      > And I could be wrong, but I thought SQL is specifically for relational databases.

      It was meant to. Only that IBM suits have put programmers in charge of the project (System R), programmers who never got the relational model at all, and steadfastly refused to hear input from Mr Codd (the RM inventor) and others, so in the end Mr Codd left IBM in disgust. He got sick and had to stop evangelising the RM, and all these unrepentant SQL vendors never offered him anything for his invention.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    52. Re:Firebird(tm) and why I just don't care by leandrod · · Score: 1
      > there isn't a database I've seen that fully implements the relational model.

      At this list there are some. Not all of them are mature or fully relational, but all are better than SQL was at their own time. Some are available, and at least one used in production systems.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    53. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      If there were two people, one a petite female called Sam, and another a large male called Sam, and I told you to hit Sam, who would you hit? After all, one of them is small and female and the other is big and male - kinda hard to confuse the two, I should think.

    54. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Well, the reason for the email (which was not intended like how it worked out), was that the first "official" Mozilla response was: "it's legal, get over it".

      Now, that hurts...

      But, all is solved now.

    55. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      but slashdot users did not decide to start posting on moillazine. i'm sure 99% of the people making noise on mozillazine and the main mozilla forum were from firebirddb.

      and go back and read the slashdot articles. i remember the opinions being roughly split between the two sides.

    56. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      Hey, that's actually a pretty good, non-bias writeup of the events you've written up. But I think you forgot to mention that Mozilla in conjunction with AOL Legal researched the name for several months and didn't announce it until they had thought all issues had been resolved. I don't know for sure, but I think they were much more concerned with Firebird BBS and the distributor of the Firebird computer game, etc than they were with FirebirdDB since these products had pre-existed the FirebirdDB project. Anyway, that's my take on it.

      I can see both sides, but it still makes me wonder why on earth the FirebirdDB team would choose name as common name as "Firebird" if they valued being uniquely identified so much. They must have surely known that other software projects would eventually come along to take the name as well (along with the ones that already existed). Perhaps I'm missing an important point, but I feel the FirebirdDB people brought this unto themselves and acted unprofessionally when they realized their mistake. Or perhaps they felt that they had been able to duke it out with Borland and thought that they could take on anyone else that came around.

      Anyway, feel free to rebuttal.

    57. Re:Firebird(tm) and why I just don't care by Anonymous Coward · · Score: 0

      well, didn't they had spent several months working with AOL Legal over the issue before finally deciding on Firebird? so they were like, "yeah, we've spent a truckload of time looking into this. you're not even the first software project to use firebird, so why are you even complaining? it's legal. get over it."

    58. Re:Firebird(tm) and why I just don't care by asdfghjklqwertyuiop · · Score: 1


      The Relational Model pertains not to the physical level (DBMS engines) but to the interaction level (data languages).


      No it doesn't. It pertains to how the data is logicaly structured. Nothing at all to do with the language you use to interact with it.


      SQL is not relational. Therefore, a SQL DBMS is not relational, no matter if its engine is capable of supporting a relational language too.


      You really have no idea what you're talking about. SQL may not be purely relational, but the language you use to work with the DBMS does not dictate wether or not the DB is relational.

      Many RDBMSses allow you to use langauges other than SQL to interact with the data, in fact. In postgres for example, you can write stored procedures in other programming langauges. I hear Oracle has similar capabilities with Java.

      In theory, you can create queries on your schema in any of these RDBMSes in relational algebra. You'd have to translate that to SQL to actually use it, but doing so does not make your database non-relational.

    59. Re:Firebird(tm) and why I just don't care by leandrod · · Score: 1
      It pertains to how the data is logicaly structured. Nothing at all to do with the language you use to interact with it.

      The language must follow the logical structure, can't you see that?

      OK then, you could create a DBMS without a proper language, just an API. But that is not the case in SQL, nor in D&D's D.

      > Many RDBMSses allow you to use langauges other than SQL to interact with the data

      First, these aren't RDBMSs you are talking about, but SQL DBMSs. Because they don't support any relational languages, they don't support relational databases (that's what you mean by 'logical structures'), and even if they did, SQL access would break Codd's 12 rules.

      BTW, Alphora Dataphor do is a RDBMS (they call it 'virtual' for they don't yet have a storage engine), and it does have something like SQL. But to preserve the database sanity, they had to severily change SQL, creating a sanitised 'RealSQL'.

      Second, these other languages do have to conform to SQL's limitations and stupidities, inclusive because the database is defined in non-relational SQL, and because SQL does mixes the logical and physical structures.

      > you can create queries on your schema in any of these RDBMSes in relational algebra.

      Do that. Seriously, try it. Now how will that fare with databases defined with duplicates, NULLs, without real user-defined types etc?

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    60. Re:Firebird(tm) and why I just don't care by cubic6 · · Score: 1

      Thanks. I'll check them out.

      --
      Karma: Contrapositive
    61. Re:Firebird(tm) and why I just don't care by asdfghjklqwertyuiop · · Score: 1

      First, these aren't RDBMSs you are talking about, but SQL DBMSs. Because they don't support any relational languages, they don't support relational databases (that's what you mean by 'logical structures'), and even if they did, SQL access would break Codd's 12 rules.

      I will give you that most currently available DBMSes do not fully adhere to Codd's 12 relational rules (namely 6,7,9 and 12). But I don't see how adding SQL will break a database's conformance to the rules. Specificly which rules will be broken?


      Second, these other languages do have to conform to SQL's limitations and stupidities, inclusive because the database is defined in non-relational SQL, and because SQL does mixes the logical and physical structures.


      How does SQL mix the logical and physical structures?

      you can create queries on your schema in any of these RDBMSes in relational algebra

      Do that. Seriously, try it. Now how will that fare with databases defined with duplicates, NULLs, without real user-defined types etc?


      I'll also concede that you can build a database in postgres or oracle that breaks the relational model (by allowing duplicate rows, for instance), but you don't have to create such a database in these DBMSses.

    62. Re:Firebird(tm) and why I just don't care by leandrod · · Score: 1
      > which rules will be broken?

      Allowing non-relational access to the database. Allowing duplicates, and non-values.

      > How does SQL mix the logical and physical structures?

      For example, views are non-updateable relations.

      > you can build a database in postgres or oracle that breaks the relational model (by allowing duplicate rows, for instance), but you don't have to create such a database in these DBMSses.

      OK, here we agree. You can always define keys, always use SELECT DISTINCT. It is just that it is a pain, will perform poorly and be severily limitated as compared to relational systems.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    63. Re:Firebird(tm) and why I just don't care by Arioch_BDV · · Score: 1

      No imagine that i purchased PC off-the-shelf. Imagine there is Linux pre-installed. Now imagine that i try to install some other software, that need Firebird(DB) How soon i, beeing dummy, will realise that the Firbird browser, in which i read the help for theprogram is not the Firebird that program is asking for ? What if such a program is pre-installed to, and i will need an assistance? Those HowTo's written by superminds for superminds - will they make it clear for dummy me that 'start firebird' suggestion has nothing with 'launch Mozilla' ? What if both projects will choose to keep there configuration in same folder /etc/firebird ? The very fact of FireFox name shows there was some point. Though FibirdDB community indeed was not polite. To some excuse may be 1st posts on Mozilla's forum when they choosed the Firebird title. Someone pointed that the name was always taken - and immediately replied with notes like 'go away! who are You? No one knows of You! We are lefgion, We are power, get away from our marching' Indeed it is hard to believe that no one had known of FirebirdDB project - Sourceforge is one of the famoust sites and type 'firebird' in Search box coul;d be a matter of 5 seconds. Maybe it was, alas, frequent situation, when two are exchanging with blows and each new blow is 10% harder than previous one. It can rapidly come from slaps to killing.

    64. Re:Firebird(tm) and why I just don't care by leandrod · · Score: 1
      > I always believed the database was relationaly designed and interfaced via SQL but what do I know...

      Good opportunity to learn about the relational model and how SQL violates it!

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
  5. Stupid Name Change Got Me Again.... by FerretFrottage · · Score: 0

    At first I thought Firebird has a RDBMS built into it? No wonder it's so fast; it has the entire Internet in the database...then I remembered the name change. Doh

    --
    "Look Lois, the two symbols of the Republican Party: an elephant, and a fat white guy who is threatened by change."
  6. Woohoo! by DarkHelmet · · Score: 4, Funny

    I'm so glad this version of FireBird renders CSS properly... no wait...

    --
    /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
    1. Re:Woohoo! by CeleronXL · · Score: 2, Funny

      Most versions of the browser render CSS properly. O_o

    2. Re:Woohoo! by Anonymous Coward · · Score: 0

      Way to not get it. O_o

      :)

    3. Re:Woohoo! by DarkHelmet · · Score: 0, Offtopic
      Oh really?

      Are we forgetting about Internet Explorer?

      If you don't believe me, try creating a div field over a select dropdown... Horrible.

      --
      /^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
    4. Re:Woohoo! by __past__ · · Score: 1

      Well, how hard is rendering CSS anyway? Just display text/css the same way as text/plain, and everyone is happy.

    5. Re:Woohoo! by Anonymous Coward · · Score: 0

      > try creating a div field over a select dropdown..

      Hmm, last time I tried that, it didn't work in Mozilla either.

    6. Re:Woohoo! by Anonymous Coward · · Score: 0

      So not funny.

  7. Look up! is it a browser, is it a OS? by Bender+Unit+22 · · Score: 5, Funny

    no it's a database!

    1. Re:Look up! is it a browser, is it a OS? by Anonymous Coward · · Score: 0

      Let me take this opportunity to announce my own integrated dB/browser/OS project, FirePhoenixFoxBirdOS. It aims to be... um, everything.

    2. Re:Look up! is it a browser, is it a OS? by Anonymous Coward · · Score: 0

      wait a minute....

      (6 hours later)

      ...and that is why it should be called GNU/FirePhoenixFoxBirdOS.

      RMS.

    3. Re:Look up! is it a browser, is it a OS? by Sentry21 · · Score: 4, Funny

      Maybe someone can figure out how to merge it into the EMACS source tree. Then it can be all three.

      --Dan

    4. Re:Look up! is it a browser, is it a OS? by Epistax · · Score: 1

      What the f*ck is a firefox? Photoshop contest, anyone? :)

    5. Re:Look up! is it a browser, is it a OS? by nizo · · Score: 1
      What the f*ck is a firefox? Photoshop contest, anyone?

      The most feared animal in the forest, the Flaming Fox, or FireFox for short, runs through the forest, setting trees and other animals alight.

    6. Re:Look up! is it a browser, is it a OS? by kannibal_klown · · Score: 1

      Sounds like something outta Pokemon ;)

  8. Re:Firebird/fox by finkployd · · Score: 4, Informative

    It's not a matter of ease, they were around for a lot longer and had the name long before Mozilla co-opted it.

    Finkployd

  9. Ooooh, THAT firebird by Eberlin · · Score: 3, Informative

    Seriously, though -- I hadn't heard of this particular firebird before the Mozilla fiasco happened. I'm sure I can speak for a lot of folks who couldn't name this project when asked to name the OSS database apps they know.

    Of course now they'll be known as the folks that got the name "Firebird" when Firebird changed its name to Firefox. Oh yeah, and they make a database.

    1. Re:Ooooh, THAT firebird by Anonymous Coward · · Score: 0

      "I hadn't heard of this particular firebird before the Mozilla fiasco happened."

      Which is why it was a bad thing, them using the database's name. Before the browser was called Firebird, when we told a customer what database our software used they'd say 'Firebird? I haven't heard of that one', and we'd tell them it was a derivative of Interbase. Now they say things like 'Isn't that a browser?', or 'I didn't know they made databases as well as browsers', or 'Isn't it a bit silly them using the same name as a browser'.

    2. Re:Ooooh, THAT firebird by Anonymous Coward · · Score: 0

      i think you are thinking about visual fire fox pro

    3. Re:Ooooh, THAT firebird by Anonymous Coward · · Score: 0

      this is just stupid. then wouldn't it make sense for the FirebirdDB team to pick a name not as common as "Firebird." honestly, they really did this to themselves. sheesh, firebird? if they really cared about brand recognition and not cared about "sound cool" they wouldn't have choosen "firebird."

  10. mysql lets you put crap in your database by Stone316 · · Score: 2, Insightful

    The only people I know that would use mysql as the backend for anything aren't DBA's. Why? Because it allows you to put crap in your database.. This has been debated countless times on /. so there's no point going through all the points again. Lets just say any DBA worth a grain of salt wouldn't use mysql.

    --
    "Thanks to the remote control I have the attention span of a gerbil."
    1. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      Hold on to that $100k+ job as long as you can, brother.

      Websites for small - medium sized business exist solely because of MySQL or PostgreSQL. I'd be inclined to use Oracle too for those high transaction load or high capacity data stores, but for your average small/medium business with modest transaction and storage requirements it is overkill (and overpriced).

    2. Re:mysql lets you put crap in your database by ThogScully · · Score: 1

      Yeah, no worthwhile sites use MySQL. Or perhaps your needs just don't actually apply to everyone?
      -N

      --
      I've nothing to say here...
    3. Re:mysql lets you put crap in your database by mr_majestyk · · Score: 2, Interesting

      The only people I know that would use mysql as the backend for anything aren't DBA's. Why? Because it allows you to put crap in your database. This has been debated countless times on /.

      Huh? It must have been debated when I was in my coma. The post was modded "Insightful", so it must be true. Can someone please clarify what it means to "put crap in your database", and what it is about MySQL that allows it? Which FM should I read to understand the issue better?

    4. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      You're so fulla shit, Stone. :p

      TFOAE.

    5. Re:mysql lets you put crap in your database by Bender+Unit+22 · · Score: 1

      Thank god there is a database you can use and create websites/intranets without having to be a DBA. And as much as I love (and use) Oracle, it is not for those who need to make a small site with 10 Megabyes of data.

    6. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      Yeah google uses MySQL to index all those 4 billion pages. Really. They do.

    7. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      Yep thank god there is SQLite!

      http://www.hwaci.com/sw/sqlite/
      http://php.net/ sqlite

      http://snaps.php.net/win32/PECL_STABLE/php_sqlit e. dll
      http://pecl.php.net/get/SQLite-1.0.tgz

    8. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      I'd have to agree. mysql is a total POS.

      I think anyone who does any kind of work with a real RDBMS (I'm a Teradata guru) would tend to agree (not just DBA's). Hell the lack of views, strange left join behavior and several other dodgy features make MS Access look good. Hell even firebird has views.

      Now if only they'd hurry up and complete the windows native version of postgresql so i can do some complex recreational db programming :) Perhaps they could add some nice OLAP functions too (like RANK)

    9. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      MySQL may run slashdot, but Postgresql runs .org.

      Trump that bitch.

    10. Re:mysql lets you put crap in your database by WWWWolf · · Score: 1
      Because it allows you to put crap in your database.. This has been debated countless times on /.

      Isn't that a little bit redundant expression? Aren't those two the same things? =)

    11. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      Oh yeah, what's the difference between Postgresql backing .org and MySQL backing Slashdot?

      One of them NEVER CRASHES.

    12. Re:mysql lets you put crap in your database by Sxooter · · Score: 1

      Here's how:

      create table test (id int4);
      insert into test values (123456789012345);
      select * from test;
      id |
      | 2147483647 |
      1 row in set (0.01 sec)

      Huh. I could have sworn I tried to insert a number that was too big. But somehow, instead of throwing an error, MySQL just put in the biggest number it could. Would be real nice to see in an accounting system, huh?

      Check here for more problems with MySQL:

      http://sql-info.de/mysql/gotchas.html

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    13. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0
      The post was modded "Insightful", so it must be true.

      It doesn't have foreign keys, which means a good chance of data inconsistency and therefore unexpected exceptions amoung other things. The nice thing about interbase/firebird is that it is a poor mans industrial database; not as heavy as Oracle or as full featured, but good for a midsized company/project. MySql really is a flaky hodgepodge in comparison.

    14. Re:mysql lets you put crap in your database by Stone316 · · Score: 4, Informative
      You know, I run into people all the time that think they didn't or don't need a DBA. Usually, they are calling me when they can't figure something out or their system crashed and they can't recover, etc, etc. It doesn't matter if its commercial or opensource, you need a DBA. Someone who understands how to administer the environment and protect your data.

      Personally, as a DBA, I don't like mySql because of the numerous gotcha's it has unlike postgreSql. That speaks for itself... but hey, if you write bugfree code and trust that others do as well, then go ahead, use it. BTW> I'm a fan of postgreSQL, I wouldn't hesitate to recommend that if $$$ are a concern.

      --
      "Thanks to the remote control I have the attention span of a gerbil."
    15. Re:mysql lets you put crap in your database by Anonymous Coward · · Score: 0

      Actually, MySQL does support them. Unfortunately, it will also let you try to define them on table types that don't support them, and throw nary an error.

      Ugh. Everytime the MySQL crew gets something mostly right, they get the surrounding parts of it horribly wrong. sad, if they worked a little harder on things like constraints and all, it might be a good database. As it is, it just lets you make too many mistakes that wind up being like snow balls rolling down hill getting bigger and bigger, and you don't notice the data entering your database is messed up until you've got millions of rows with errors in it.

    16. Re:mysql lets you put crap in your database by Betcour · · Score: 1

      So they don't run VACUUM daily ?

    17. Re:mysql lets you put crap in your database by Betcour · · Score: 1

      SQLite is indeed fabulous, but scaling might be a tad difficult. Plus, it's a bit weird (typeless database).

  11. In other news by nebaz · · Score: 4, Funny

    Due to trademark infringement potential and other potential confusion, Firebird Database Engine has just changed its name to

    F------d Database Engine

    More news to follow.

    P.S. For any lawyers, etc. reading this, the above is an example of "parody", not subject to the definition of "slander" or "libel".

    --
    Rhymes that keep their secrets will unfold behind the clouds.There upon the rainbow is the answer to a neverending story
    1. Re:In other news by ShinyBrowncoat · · Score: 3, Funny
      Due to trademark infringement potential and other potential confusion, Firebird Database Engine has just changed its name to F------d Database Engine
      Are you sure that isn't "F----d Database Engine"?
      --

      "They've canceled the show but we're still here. What does that make us?" "Big Damn Junkies, Sir!" "Ain't we just"
    2. Re:In other news by Anonymous Coward · · Score: 1, Funny

      P.S. For any lawyers, etc. reading this, the above is an example of "parody", not subject to the definition of "slander" or "libel".

      It is, however, a very poor example. You may still be able to sue for some sort of emotional trauma.

    3. Re:In other news by ari_j · · Score: 1

      Actually, it's not subject to the definition of 'slander', regardless of what you said. Well, unless you dictated it, of course, but who'd be so stupid as to dictate a comment on Slashdot? If I had a secretary with that little to do, I'm sure something pressing would pop up.

    4. Re:In other news by nebaz · · Score: 1

      Learn something new every day. Cool.

      --
      Rhymes that keep their secrets will unfold behind the clouds.There upon the rainbow is the answer to a neverending story
    5. Re:In other news by Anonymous Coward · · Score: 0

      Firedash???

    6. Re:In other news by ari_j · · Score: 1

      A day you don't learn something new is a day wasted, I always say.

  12. Assembling static data by polv0 · · Score: 4, Interesting

    I work as a data-mining professional and aside from creating statistical models on flat-files, I manage the process of transforming and joining relational databases into a a flat file for model building.

    Currently we use Oracle for this work, but in the past we tried switching to MySQL but found that it lacked some of the key features such as materialized views, nested sub-queries and a variety of Oracle SQL functions that we find useful. MySQL seemed to be geared towards maintaining a real-time database to support customer interaction, rather than as an environment for assembling static data sources.

    Could Firebird be a viable open-source alternative, or are there others?

    1. Re:Assembling static data by Anonymous Coward · · Score: 0

      PostgreSQL

    2. Re:Assembling static data by Derek+Pomery · · Score: 2, Funny

      The features you mention are now available in 4.1 - they were never a priority since they are easily handled in code.
      Granted, subselects save on network traffic (although it seems to me it can also be done a little more clunkily with TEMPORARY tables).

      Don't see where you see this distinction between real-time and static data in MySQL, but until you're more specific about the host of Oracle features, I still won't know.

      I, on the other hand, am still annoyed that Oracle doesn't allow taking a slice of a result set and still can't do outer/left/right joins in a standard fashion.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    3. Re:Assembling static data by FlashBac · · Score: 1

      Have a look at the latest MySQL beta specs.

      --
      "Thats right buddy, the large print giveth, and the small print taketh away."
    4. Re:Assembling static data by bwt · · Score: 5, Informative

      I'm also an Oracle guy. I find MySQL loathesome and inadquate for all buy toy-level applications. I see Firebird and PostgreSQL both as viable midrange solutions. I think they each could work in settings were you aren't really stressing the newest features of Oracle, but want "standard" RDBMS functionality. Both have stored procedures, triggers, and some kinds of subqueries (at least in the WHERE clause -- oracle has them also in the from clause and even in the SELECT clause).

      I think you'll find that materialized views, at least as far as doing refresh-on-commit and query rewriting, are a really advanced feature that only Oracle has. In many warehousing or decision support applications, they are a must have feature that makes the difference between project success and failure.

      Assuming you aren't in such a high performance setting, you can often simulate a materialized view by simply populating a transformation table using stored procedures. In such settings, I think either Firebird or PostgreSQL would work fine, cost less, and avoid icky proprietary licence restrictions.

    5. Re:Assembling static data by Anonymous Coward · · Score: 0

      I don't know about firebird, but postgresql has a lot better support for things like the ones you are mentioning (subqueries being the one I miss the most when I use mysql).

      AFAIK firebird has the same feature-level as postgres (if not more).

      Search for a comparison between mysql, postgres and firebird (it is there, somewhere in the net).

      If you are used to Oracle maybe postgres is a better idea (it has Oracle style stored procedures in pl/sql).

    6. Re:Assembling static data by bwt · · Score: 3, Informative

      I, on the other hand, am still annoyed that Oracle doesn't allow taking a slice of a result set and still can't do outer/left/right joins in a standard fashion.

      What are you talking about?

      ANSI standard syntax for such joins was added two versions ago in Oracle. Personally, I hate the ANSI syntax.

      What exactly does "taking a slice" of a result set mean? Oracle gives you half a dozen different ways to do this. The standard one is to use native dynamic sql to add arbitrary WHERE clause conditions at runtime. If that isn't enough, Oracle 9i provides a far greater capability: pipelined table functions allow arbitrary programmatic construction of a result set that can be used as a table in a FROM clause.

    7. Re:Assembling static data by cirrus-global · · Score: 1

      Reading your old comments, you obviously have an interest/knowledge of this arena. What are your experiences in mining unstructured data? Text rather than numeric data?

    8. Re:Assembling static data by PongStroid · · Score: 1

      they were never a priority since they are easily handled in code.


      They are (and should be) easily handled by the database server. They are a pain in the ass to deal with on the client-side.

      Granted, subselects save on network traffic


      Yes - that's one consideration. Consider, also, the clarity of the syntax vs. a script.

      I've had numerous tasks I could have finished with a single ANSI-92 SQL statement. However, since I've been 'stuck' with MySQL on my current project I've had to resort to tedious script-monkey excercises to do the same sort of things.
    9. Re:Assembling static data by Earlybird · · Score: 2, Insightful
      What exactly does "taking a slice" of a result set mean?

      I suspect the poster is talking about linear slicing at the row level; in PostgreSQL, for example, you can do select ... where ... limit 25 offset 50 to get rows 50-74 of a result set. MySQL has a similar syntax. Oracle supports a size limiting clause, but I don't remember if it has a way to specify the starting offset.

    10. Re:Assembling static data by Mubarmij · · Score: 1

      Firebird does have subelects in the Select part of the query.. but not in the From part..

    11. Re:Assembling static data by Anonymous Coward · · Score: 0

      Both have stored procedures, triggers, and some kinds of subqueries (at least in the WHERE clause -- oracle has them also in the from clause and even in the SELECT clause).

      Postgresql has allowed you to place subselects in the select or from clauses for quite some time.

    12. Re:Assembling static data by Anonymous Coward · · Score: 0

      No check out MaxDB

      Particularly ORACLE MODE... ./'ers like to talk about mySQL but compared to MaxDB it truly is a toy...

    13. Re:Assembling static data by polv0 · · Score: 1

      I have limited experience mining text/unstructured data. In the past I have used word-frequency counts to mine semi-structured text.

    14. Re:Assembling static data by Derek+Pomery · · Score: 1

      Hm. Will have to recheck that at work. We are running Oracle 9i and I assure you queries were *breaking* that we tried to do left joins on.

      We ended up just handling it in code.
      As for the slice thing, the other respondant is exactly right. And that's a very handy thing to do.
      But yes, Oracle *does* let you limit a query, which can be made to work similarly depending on circumstances and your patience.

      --
      -- perl -e'print pack"H*","6e656d6f406d38792e6f7267"' /. ate my old sig. Bastards.
    15. Re:Assembling static data by Arioch_BDV · · Score: 1

      AS: there are special data storage servers for datamining, not RDBMS, or based upon RDBMS. Maybe try some of them?

      IB-clones do not have meterialized views.
      You can add functions yourself, with external DLL (SO) file - they are called UDF - user-defined functions.

      Yaffil team is now adding more SDFs (server-defined functions) to meet some of MSSQL and Oracle.
      So later they might appear in Firebird 1.6 or 2.0

      But usually datamining starts at gigabytes or maybe terabytes of raw data.
      Why FB is capable of working with tens of GB, i'm sure it will not fly beeing loaded with TBs of data :-)

    16. Re:Assembling static data by Arioch_BDV · · Score: 1

      The can be hanfled 'in code' 'by the database server' - triggers.

  13. How do I use this thing? by lawpoop · · Score: 1

    They don't make this apparent in their homepage. How do I use this? Is there an ODBC driver? Can I talk to it with a PHP driven website?

    --
    Computers are useless. They can only give you answers.
    -- Pablo Picasso
    1. Re:How do I use this thing? by Anonymous Coward · · Score: 0

      RTFM, my dear.

    2. Re:How do I use this thing? by zippity8 · · Score: 1, Redundant

      AFAIK, Firebird still retains the same interface as Interbase.

      This means that PHP4.0 has full support for it -- but I'm not sure how this applies with the new version of firebird.

      http://www.php.net/manual/en/ref.ibase.php
      http ://www.ibphoenix.com/a6181.htm

    3. Re:How do I use this thing? by arf_barf · · Score: 3, Informative

      What language? What platform?

      Let's start with a nice Win32 Gui to administer the db: IBExpert

      OK, now the drivers: there are plenty of ODBC, OleDB, .NET and JDBC drivers available. I personally use IBProvider, it's a OleDB driver. I have also used the open sourced ODBC driver with great success.

  14. Right by pheared · · Score: 4, Funny

    So, I typed in slashdot.org but somehow I ended up on freshmeat.net. wtf?

    1. Re:Right by fm6 · · Score: 4, Funny

      If this were another pointless MySQL upgrade, you'd have a point. But this is a real database.

    2. Re:Right by Anonymous Coward · · Score: 0

      If this were another pointless MySQL upgrade, you'd have a point. But this is a real database.

      And this database a real license as well. Not a fake GPL that is truly meant to ensnare its users in confusion and is not free.

    3. Re:Right by Directrix1 · · Score: 1

      No joke. People really talk down to a database which is probably superior to the one they have. MySQL's feature set is nothing compared to Firebird. Firebird's license is far less restrictive. Firebird runs on a bazillion platforms. And there is documentation for it, not to mention an embedded build. Also, it has a nice no maintenance attitude. As in it can run for quite a long time without having to perform any maintenance chores on it. Also, it implements almost all (if not all) of SQL92 and a sizable chunck of SQL99. This is a nice full featured server, and anyone who just throws this off is doing themselves a great discredit.

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
  15. Re:What torrent? by Anonymous Coward · · Score: 1, Informative

    No, I didn't
    it's right here

    Any idiot could of figured that out.

  16. No thanks. by Fizzlewhiff · · Score: 1

    I'm waiting for their more resource efficient Sunbird product.

    --

    'Same speed C but faster'
    1. Re:No thanks. by petabyte · · Score: 1

      Umm, no, Sunbird is a Mozilla product. Its the standalone version of their Calender.

  17. Only got one thing to say about Firebird: by Cecil · · Score: 1

    I love PostgreSQL. It's OO, blazingly fast, easy to install, robust, and free as free can be. All sorts of things that Firebird is not. And the name doesn't have a chance of *ever* conflicting with anything. Hah.

    1. Re:Only got one thing to say about Firebird: by AKnightCowboy · · Score: 1
      I love PostgreSQL. It's OO, blazingly fast, easy to install, robust, and free as free can be.

      Easy to install? I guess if you've installed it before. I found it amazingly complicated to install and never did get it working right. I ditched it for MySQL which was much simpler. I never need to screw around with the pg_hba.conf file (or whatever it is) to setup access permissions.

    2. Re:Only got one thing to say about Firebird: by Anonymous Coward · · Score: 0

      Well, firebird is blazingly fast, easy to install, robust, and free as free can be, what's your point exactly? That it is not OO?

    3. Re:Only got one thing to say about Firebird: by Anonymous Coward · · Score: 4, Funny

      Mysql easy?? I couldn't even begin to get it to install so I had to revert old school and use a sheets of paper and a filing cabinet for my database.

    4. Re:Only got one thing to say about Firebird: by Anonymous Coward · · Score: 0

      I hope this helps: http://www.postgresql.org/docs/7.3/interactive/cli ent-authentication.html#AUTH-PG-HBA-CONF (scroll down to the examples part..)

      What you want is this:
      local all all md5
      host all all 127.0.0.1 255.255.255.255 md5

    5. Re:Only got one thing to say about Firebird: by Sxooter · · Score: 2, Informative

      I too love postgresql, but let's be honest:

      1: The OO stuff as regards table inheritence is broken, and no one's in a hurry to fix it.
      2: It's easy for me to install, for some people, not so much.
      3: FirebirdSQL is just as free as PostgreSQL, using their own version of the Mozilla Public License.

      The main things that PostgreSQL is that FirebirdSQL is not is heavily tested in enterprise environments. Remember, every time you go to slashdot.org, the database serving up that site is MySQL, but the database serving up the IP for that .org site is PostgreSQL.

      However, I totally agree there's a negative probability that anyone will ever use the name Postgresql for any other project.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    6. Re:Only got one thing to say about Firebird: by __past__ · · Score: 2, Informative
      PostgreSQL is trivial to install. Actually, there was a binary package for just about any unix-like OS I ever wanted to run it on. Compiling it from source is not hard either, even if there are more steps involved that just "configure; make; make install", due to it not running as root, which is a good thing.

      Configuration, what you seem to be talking about, is not rocket science either. Of course it is harder than configuring MySQL, because it does more. In the case of access permissions, PostgreSQL seperates database permissions (GRANT SELECT ON some_table TO some_user) and the right to connect to the server in the first place (which you set up in pg_hba.conf). This is more work than the pure GRANT-based scheme of MySQL, where GRANTs not only based on user id, but also the remote host etc. It is also more flexible - For example, PostgreSQL can authenticate a connection with Kerberos or PAM - as far as I know, this is not possible, or at least not trivial, with MySQL.

      As always, both have their place. If you want easy, use MySQL. If you want flexible, use PostgreSQL. Firebird's claim to fame in this regard has to be filled in by someone else, I don't know it well enough :-)

    7. Re:Only got one thing to say about Firebird: by aled · · Score: 1

      At least with Firebird the database is in one file, I don't even want to know what My(your?)Sql does with databases files...
      I said I don't want to know!

      --

      "I think this line is mostly filler"
    8. Re:Only got one thing to say about Firebird: by Anonymous Coward · · Score: 0

      The parent to this post may be somewhat insulting, but it's hardly flamebait.

      MyISAMcheck is a big old pain the butt, and everyone I know who runs MySQL is familiar with it.

      The parent to the parent of this post was obviously posted by someone who installed postgresql, read the docs for 30 seconds, and gave up because it was too hard.

      Since when is challenging someone's geek status flamebait anyway. Lame fucking moderators...

    9. Re:Only got one thing to say about Firebird: by C_Kode · · Score: 1

      I wrote my database all in one source file too. Why people bitch I don't know. You should check it out. It's called Singularity.cppSQL-DB :)

    10. Re:Only got one thing to say about Firebird: by Joe+Enduser · · Score: 1

      They should really rename that license. I think there is already an open source project by that name.

    11. Re:Only got one thing to say about Firebird: by Sxooter · · Score: 1

      I guess Irony can be pretty ironic sometimes...

      (A quote from the old Police Squad show...)

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    12. Re:Only got one thing to say about Firebird: by sharkey · · Score: 1
      I had to revert old school and use a sheets of paper and a filing cabinet for my database.

      Sheets of paper!?!? Filing cabinet!?!? You lucky bastard! In my day, we had to scratch our records onto limestone rocks with our fingernails, and then put them in our beds to use as mattresses. Kids these days...

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  18. And they may have to change it again by Anonymous Coward · · Score: 0

    A company called FIREFOX used to exist in the UK,
    and yes, it manufactured software.

  19. Re:Who fucking cares? by Anonymous Coward · · Score: 3, Funny

    Wow, two troll posts. You buy a sco license too?

  20. Pain in the ass to build by mr_majestyk · · Score: 4, Informative

    I tried building the Firebird code a few months ago, and found out that step 1 is...

    ...start with a running version of Firebird!

    Bootstrapping might seem like a K00l trick, but there is something uncomfortable about self-referential build procedures (not to mention that it was a pain in the ass to find a preexisting version of Firebird to run).

    Gimme a pile of c/cpp & h files and let me build it from scratch, dammit!

    Is that possible today? Dunno...the build guide appears to be still under construction.

    1. Re:Pain in the ass to build by jamesots · · Score: 4, Informative

      That would have been Firebird 1, which was just a slight cleanup of the (very) old Interbase code, and I'll agree, the build process was terrible.

      Firebird 1.5 has been ported to C++ and doesn't need to be bootstrapped from an existing installation, just configure and make it.

      --
      Ho hum for the life of a bear
    2. Re:Pain in the ass to build by Anonymous Coward · · Score: 0

      Obviously your using the old fb1 version, build system was much as it was as released.

      But much work has been done strightening out the build process

      so try:

      $./configure
      $make
      $make packages
      $make install

      win32 has a similar setup.

      Cheers

      Mark

  21. Oh, the stupidity... by agoliveira · · Score: 5, Insightful

    Why are you people bashing so hard about the naming issue? You know what? I don't care!
    I know Firebird DB since it's earlier days and I was a Interbase user before that. And I loved it. Why? Because the kind of job I did that time required a simple, efective, maintence-free database and Firebird is exactly that. You can just install it and forget it. The whole database is just one file (at least was) so a simple tar or zip will backup your stuff.
    Yeah, yeah, I know there is MySQL, PostgreSQL, etc but as I said, I'm not on this kind of job anymore and even if I was, while firebird does what I want (and well) why should I care about other RDBMS?

    --
    Scientia est Potentia
    1. Re:Oh, the stupidity... by Just+Some+Guy · · Score: 4, Interesting
      The whole database is just one file (at least was) so a simple tar or zip will backup your stuff.

      That's all well and good, except that you're completely wrong. First, you can back up any database that uses OS-level files using tar and gzip - that's certainly nothing special for Interbase/Firebird. Second, we experienced table corruptions constantly that resulted in rows that were still present in the table, but couldn't be fetched. Relational integrity means jack squat when referenced rows suddenly cease to be accessible.

      Interbase/Firebird obviously worked for at least some people, or else it would've been altogether dropped years ago, but it's bitten enough people that it's just not accurate to call it "maintence-free" (unless that has a backhand slam at the abyssmal state of the administrative tools, and you meant "-free" as in "-not-capable-of").

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Oh, the stupidity... by agoliveira · · Score: 1

      Sorry but I'm not *completely wrong*. Is anything wrong about what I said? I agree with you. My statemment wasn't precise, after I read it again I saw it but from that to say that I'm "completely wrong" it's a long way.
      As I said it worked quite well *for me* (and I'm not doing this kind of job anymore). I never said I was (or am) a DBA.
      And, again, for me *was* "maintence-free" as usualy my customers at that time was small offices and shops with no IT literate people around and when I used interbase, sometimes people did the database backup dragging and dropping the database file to the local machine.
      Got it?

      --
      Scientia est Potentia
    3. Re:Oh, the stupidity... by Anonymous Coward · · Score: 1, Informative

      Any reason not to use the "gbak" application included with Interbase/Firbird to backup you database?

    4. Re:Oh, the stupidity... by Just+Some+Guy · · Score: 1
      You asserted that Firebird is a maintenance-free system. It provably is not, as there is plenty of anecdotal evidence that many people have had problems with it over the years. I won't argue that it wasn't stable on your system, because that would be silly, but saying that one instance of a product runs well is not the same as saying that the product itself runs well.

      I might've been over-assertive, but you wouldn't believe the hassle that this particular system put me and my employers through.

      --
      Dewey, what part of this looks like authorities should be involved?
    5. Re:Oh, the stupidity... by Just+Some+Guy · · Score: 1

      Yes. It didn't work at all on corrupted tables. I originally wrote the "dbreplicate" that I mentioned in an earlier post for the precise reason that gbak would always segfault when it tried to read certain tables, and it was absolutely critical that we be able to salvage as much information from those as possible (off-topic - the tables had silently failed longer ago than the rotation cycle of our regular backups before we ever found the corruption).

      --
      Dewey, what part of this looks like authorities should be involved?
    6. Re:Oh, the stupidity... by nconway · · Score: 3, Informative
      First, you can back up any database that uses OS-level files using tar and gzip - that's certainly nothing special for Interbase/Firebird.


      Uh, no. A typical modern RDBMS will use a scheme similar to WAL (write ahead logging) to record data changes and allow recovery from crashes. Unless you can manage to make tar+gzip atomic (which is true if you're using a filesystem-level snapshot feature, but not true if you're actually using tar), you won't get a consistent on-disk snapshot of a DBMS like that. The reason is that the WAL and the data files will be out of sync.

      In order to effectively back up such a database using tar, you need to shut down the DBMS (which is hardly an appropriate backup technique),
    7. Re:Oh, the stupidity... by Just+Some+Guy · · Score: 1

      Your entire argument is 100% correct, and also applies in exactly the same way to the grandparent post. I certainly didn't mean to imply that you could backup a running database with tar, and I don't think that the grandparent did either.

      --
      Dewey, what part of this looks like authorities should be involved?
    8. Re:Oh, the stupidity... by egoots · · Score: 1

      Out of curiosity, what version of Interbase were you running? My understanding is that Borland released a couple of really buggy versions prior to the 6.0 release (which was open sourced).

      As far as I know, you shouldnt be copying the file unless you are sure the dbase server isnt accessing it (which can happen when a background sweep occurs)... that is the purpose of Gbak... so you can do backups online in a snapshot transaction

      Just to make sure I understand, that you are complaining that their gbak utiltity didnt work on corrupted files? I thought the idea was that you backed up before the files got corrupted, and resotred the good copy?

    9. Re:Oh, the stupidity... by Just+Some+Guy · · Score: 1
      We were running the open source version, I'm almost certain. I came into the company after the server was well established, so I'm not completely sure of what was current at the time of installation.

      Furthermore, I have no idea of what the backup procedure was before I came onboard. I do know that the database contained many errors when I started, and that they weren't readily apparent until I started auditing the backup logs and conducting tests.

      Yes, you are correct - gbak didn't work at all on the corrupted files.

      --
      Dewey, what part of this looks like authorities should be involved?
    10. Re:Oh, the stupidity... by Anonymous Coward · · Score: 0

      You're a fucking liar.

      Got it?

      Self-servient fucking prick.

    11. Re:Oh, the stupidity... by Anonymous Coward · · Score: 0
      You can backup any database with tar and gzip, as long as it is not running.

      If you want to backup from a running Firebird/Interbase database, try the gbak program.

    12. Re:Oh, the stupidity... by Arioch_BDV · · Score: 1

      Did You try special options of GBACK and GFIX ?
      They are described in manual.

      But You are right, IB 6 OS ,and IB 5.x before 5.6 are known to be buggy.

      Maybe You never will find them, but trying to do something complex - You will certainly nned to understand inner engine to avoid them.

      PS: gback never warranted that You will succesfully restore database that You successfully backed up.
      Simplest way it to alter table, makeing some column constrained as 'NOT NULL' while cintainning NULL values. This database will be easily backed up and never restored (without special options, descibed in manual)
      I've heard of nback for Firbird project though.

    13. Re:Oh, the stupidity... by Anonymous Coward · · Score: 0

      well, using freebsd 5.X new filesystem snapshot, maybe. But most database will have a severe time skew if you just start taring away on the files.
      Now, you can shut them down and back up using the OS tar, but then your db is offline.

  22. marketing... by Unominous+Coward · · Score: 3, Funny

    You know what, a good product often has to revamp its image in order to accelerate takeup. I suggest they change their name to something fiesty, energetic and powerful-sounding.

    Why not combine the fiestyness of a fox with the power of fire. I suggest something like Foxfire or Firefox!

    --
    "Smoking helps you lose weight - one lung at a time" -- A. E. Neumann
    1. Re:marketing... by aled · · Score: 1

      Foxbird?

      --

      "I think this line is mostly filler"
    2. Re:marketing... by Anonymous Coward · · Score: 0

      Why not DushFlushTec Inc.?

      Cheers,

      --Coder

  23. One Firebird... by holizz · · Score: 5, Funny

    to serve up pages, one to view them... and one Firebird to rule them all?

    1. Re:One Firebird... by NerdSlayer · · Score: 3, Funny

      One football player to beat you, a wrestler to throw you... and one cheerleader to laugh at your fall.

  24. Re:SQL not relational by Anonymous Coward · · Score: 2, Funny

    >SQL is not relational. Its tables are not relations, because relations are sets, and sets don't contain duplicates.

    Yeah, but if you relationate without any protection, you're going to somehow end up with look-alike duplicates...

  25. Re:Firebird/fox by errxn · · Score: 1

    ...so if I named one of my turds "slashdot" in 1983...

    I'm afraid that's stretching the definition of 'prior art' to its very limit.

    --
    In Soviet Russia, Chuck Norris will still kick your ass.
  26. Can anyone actually run it? by Anonymous Coward · · Score: 1, Interesting

    So how many slashdotters actually downloaded it and attempted to run? The damn thing doesn't even compile on RedHat 9.0 with the latest GCC.

    1. Re:Can anyone actually run it? by Anonymous Coward · · Score: 0

      Oh please, plenty of stuff refuses to compile under RH9. Postgresql had issues at first too. RH moved all kinds of shit around in 9. It's so bad that many things compile better under Fedora than RH9

    2. Re:Can anyone actually run it? by Anonymous Coward · · Score: 0

      No, the RH9 distribution isn't that great. In essence, a misconfigured mess.

    3. Re:Can anyone actually run it? by Anonymous Coward · · Score: 0

      Gee, Redhat == Linux?

      My god, we need a better class of trolls around here, this ones an idiot.

      RH linux has issues. There are still some 300+ distros out there. you can change, try another, use fedora (which you'll notive I mentioned as solving this issue).

      But, that's not usability, you fucking moron, that's administration. Usability has to do with things like running applications, exporting your data, etc...

      God, you'd think that the MS shills / trolls would at least take a logic course or two...

      fucknut.

  27. Re:Firebird/fox by finkployd · · Score: 2, Informative

    Not quite true, it cause some maning conflicts in some distros (in gentoo firebird refers to the DB and mozilla-firebird refered to the browser).

    How hard is it really to do a search on freshmeat, sourceforge, and google before you name a project? I do it all the time.

    Plus it isn't like it was a dead project or a one person project, it had a (albiet not MySQL size) following and was under active development.

    Sorry, I love Mozilla but they were in the wrong here.

    Finkployd

  28. Re:Drum roll please... by Anonymous Coward · · Score: 0

    sunnuvabitch! I liked it better when It was a browser.

  29. Re:SQL not relational by Anonymous Coward · · Score: 2, Informative

    Rows have implicit unique row ids which make each row unique. So, there are no duplicates.

  30. don't jump to conclusions by VegetariMan · · Score: 2, Insightful

    I don't know a thing about Firebird, but I'm not prepared to dismiss it simply because of a name conflict with Firefox. Maybe it's a great database. Maybe they didn't treat Firefox fairly when disputing the duplicate name. Maybe they had a legitimate right to their name and the Mozilla folks should have been more diligent about picking a name.

    Either way, I doubt the people at Firebird deserve the occasional vitriol from others on this thread.

    --
    --Nick
  31. Re:ok by mfivis · · Score: 1

    it could do without the curses, but other than that, I completely agree.

  32. An extremly light weight SQL Engine? by ciroknight · · Score: 2, Funny

    Well, firebird is definitely a good contender, but I still want a database server that's fast and small... and the faster and smaller the better. Problem is I need most of the features you'll see in a high end one, and I need it to be open source.. SQLite was actually a contender at one point, but I want replication as well.. so.. my question is when is someone gonna fill this niche?

    --
    "Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
    1. Re:An extremly light weight SQL Engine? by greenhide · · Score: 4, Insightful

      I don't think there's ever going to be a truly light and fast database server that pleases everybody.

      Why?

      Because to please everyone, you have to...please every one. Which means to offer the features they need. And even if you're an ace programmer, I don't think it's all that easy to de-couple the code to the point that you can just flip a few compiler flags and add or remove features at will.

      For instance, all you need is replication. What if someone else doesn't give flying rip about replication, but needs 100% Ansi SQL 99 compliance (something that very few database servers seem to have, oddly). In the stable releases of MySQL, subqueries aren't available. Subqueries! Don't tell me that you can always do the query some other way; I want my subqueries. So I opted for the heavier Postgres engine. When MySQL's stable version offers subqueries, I may switch to it, but at this point I'm fairly familiar with Postgres and don't necessarily want to risk having to rewrite thousands of lines of query code ("Standard" Query Language?!? *What* standard?)

      Because there's no one group to please, I don't think anyone's ever going to "fill this niche" because there are a hundred other niches that need filling -- after all, for some people, internationalization and ISO Latin capabilities are crucial; for others, it's roughage.

      Database development takes a while -- or at least, it takes a while to do well. There are a ton of MP3 players out there that actually work, but very few database servers that do. It requires a lot of mathematical, computational, and algorithmic knowledge, as well as being kept up to date on the latest in sorting methodolgies, matrices calculations and who knows what else (I sure don't!). So it's only really "profitable" to have one database project that offers all of the features people ask for, rather then 5 that cater to different preferences. Even "bulky" database servers like Postgres seem to run fine on what are today considered "obsolete" computers, so "fast" and "small" are not really the number one criteria anymore.

      --
      Karma: Chevy Kavalierma.
    2. Re:An extremly light weight SQL Engine? by Sxooter · · Score: 4, Insightful

      Ohhh. and I need a dump truck that's fast and small, but can carry 28 metric tonnes of stone at the same time. And it needs a built in hot tub. And a satellite dish.

      Comon, every piece of software is a compromise. If you need a lot of features, then it isn't gonna be small. If you need it small and fast it's gonna be missing some features.

      Fast, featureful, small. Pick two.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    3. Re:An extremly light weight SQL Engine? by CodeMunch · · Score: 2, Interesting
      ("Standard" Query Language?!? *What* standard?)

      The generally accepted value for SQL is: Structured Query Language

    4. Re:An extremly light weight SQL Engine? by greenhide · · Score: 1

      Still, it's No wonder that I was confused.

      --
      Karma: Chevy Kavalierma.
    5. Re:An extremly light weight SQL Engine? by mugnyte · · Score: 1

      oh but i think it's a "hard problem" but not an unsolvable one.

      When on a project that needed fairly basic "data store" capabilities, we wrote it, a C++ lib. Then, some basic searching capabilities were necessary, the API was expanded. Then, indexes were added for performance (larger API). Then persistance, serialization, RI. (we never touched replication, but it is again, solvable). Another layer for simple SQL was added later, including DDL. This was a higher level API.

      Then it was wrapped in COM and exposed through SOAP, a high level API. Need ceased there, so programming did as well. Starting with simple set theory and working up to a database takes a lot of research anyway - but i contest it is possible.

      I think what people forget is that to have "capabilities" of a relational database, one must partition the behaviors adequately. Performance may suffer in terms of footprint, stack hops, or sheer number of modules, but this is how ala carte API's work, to me. Compilation tricks could be performed for building it with certain capabilities, but then you're relying on the architecture you chose for construction.

      It can be done, but since competition is rough (just read any flamewar on products), people would rather have a all the features optimized into a monolithic engine than a series of simple ones that perhaps were a bit more cumbersome.

    6. Re:An extremly light weight SQL Engine? by Anonymous Coward · · Score: 0

      This sounds like Linus Torvalds opinion too -- there's no point making a Linux kernel for highend and Linux kernel for desktops. By making everyone use the same base (with config options rather than forks) everyone benefits from a larger user base thus more testing, and more modular code.

    7. Re:An extremly light weight SQL Engine? by Anonymous Coward · · Score: 0

      "we wrote it, a C++ lib" "API was expanded" "larger API" "Another layer" "including DDL" "Then it was wrapped in COM and exposed through SOAP, a high level API"

      And then it was slow as fuck. Really, though, that's ridiculous.

    8. Re:An extremly light weight SQL Engine? by 1HandClapping · · Score: 1
      It's been over four years since I used it but SQLAnywhere was a full featured DBMS with transactions, stored procedures, and DB replication.

      They had a great support department, but were loosing their small market share

      They came out with an embedded/PDA version. You ran your application with full coverage (Sample of all types of SQL code needed). The "embedder" logged which features of the DBMS you used, then you could recompile the DBMS with a minimal footprint. If all you did was simple selects the footprint was about 16K. But if you needed transaction, stored procedures, Java Virtual machine, etc. those features could be compiled in as needed.

    9. Re:An extremly light weight SQL Engine? by Anonymous Coward · · Score: 0

      Um, that would be "Structured Query Language".

    10. Re:An extremly light weight SQL Engine? by mugnyte · · Score: 1

      Not really. It accepted a collection of SQL and returned multiple resutls in one pass. Granted, without the background about our process structure - I would agree with you on the info you've read, but it was very cool indeed.

  33. I just installed it..... by mojo17 · · Score: 0, Redundant

    ...but i cannot seem to find the Tabbed Browsing thingie :(.

  34. For those of you hung up on the whole name issue by greenhide · · Score: 3, Insightful

    If you go to the Firebird Project website, you'll see they feature, quite respectfully, Mozilla's recent decision to change their name to Firefox. Remember that the Mozilla team has gone through a lot of name changes. Camino was changed to Chimera, and Phoenix was changed to the rather unfortunate "Firebird" which was already a project name. So it's not like the name "Firebird" was all that entrenched.

    I think it's a symptom of Mozilla both try to brand, and being an Open Source project in which one monolithic product was split into various and sundry projects, each of which got bizarely named. I mean, there's nothing about any of the application titles that indicates its use or purpose.

    I myself vote for MozillaMail and MozillaBrowser or something of that ilk instead of Thunderbird and Firefox. Then the package now called "Mozilla" could be renamed to MozillaComplete or something like that.

    --
    Karma: Chevy Kavalierma.
  35. What did they have to do with it? by PigeonGB · · Score: 1

    I thought that the Mozilla people were the ones who realized that they had taken a name of another Free/Open Source project, and they decided to change it. I didn't know anything about Firebird's developers acting like asses about it. Where did this info come from?

    --
    I have 3656.9 Bogomips. How many Bogomips do you have?
    1. Re:What did they have to do with it? by Anonymous Coward · · Score: 0

      i think they went all immature on mozilla. flamed mozillazine forums. then flamed the regular mozilla forums (also located on mozillazine). then sent massive amounts of mail to the mozilla developers. very big news. kinda hard to have missed it while it was happening. very unprofessional on their part IMHO.

  36. Re:SQL not relational by AndroidCat · · Score: 1

    And we should trust that web site as authoritative because...? The all-caps page title doesn't inspire confidence. Is this "Proof by Google"?

    --
    One line blog. I hear that they're called Twitters now.
  37. Under whelmed by Anonymous Coward · · Score: 3, Insightful

    There appears to be two broad groups on this site - the useful ones (you know their posts when you see them) and the other group.
    Most of the posts I'm seeing here so far belong in the other group. Today they can't seem to get past a naming issue (which the DB had first BTW), and appear to have no interest in what the product is.
    When you are reading *and writing* to your database and there is money attached to the data integrity, this product will be fine. MySQL will not. Just imagine that you are penalised personally $1000 for every data munge that occurs in your database? I imagine that your affinity to the MySQL mindset will start to wane rather quickly.
    This database is right up with PostgreSQL and as an added bonus Firebird can be deployed on Windows and Linux. (Plus StroredProcs and Triggers galore)

    If all you can focus on however, is the project name, then be angry that Mozilla rudely co-opted the name that the DB first owned.

    And to all the slashdotters that despair at the rising tide of inane useless postings - well, you are not alone. Slashdot used to be about geek topics for geeks. New product releases, gotchas, advice, interesting hardware hacks, solving problems with FOSS etc. Now I must content myself with the current posting selections.

    And now the ultimate tirade: If you want to feed your geek/technical fetish, it's getting to the point where you'd do better watching McGyver or something.

    AC

    1. Re:Under whelmed by sbermunk · · Score: 2, Informative

      I think you are being a bit unfair to mysql. You may have experience with isam/myisam tables under mysql - I agree that those are terrible. At my workplace we had no end of troubles with mysql and myisam tables. Since we upgraded to InnoDB format, we have not had one problem in two years of heavy use. I believe I read that mysql is going to use InnoDB as its standard storage engine in the future (version 5 and up?).

    2. Re:Under whelmed by Sxooter · · Score: 1

      unfortunately, MySQL still has many other issues that innodb tables cannot fix.

      It allows you to insert a data of 0000-00-00.
      It allows you to overflow an int field with no error.
      There are others. Google search for "mysql gotchas"

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    3. Re:Under whelmed by Betcour · · Score: 1

      I consider those two points as features. You just need to be aware of them, that's all. They are design decisions (which might not please everybody).

    4. Re:Under whelmed by Sxooter · · Score: 1

      Sorry, but the SQL spec specifically says those are bugs, not features. You shouldn't have to work around bugs in a SQL database in order to have coherent data. If you don't understand that point, you probably shouldn't be programming database applications that hold any kind of critical information. Imagine a bug like that popping up in the middle of a bank year, and only being caught several months later. Disaster.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
    5. Re:Under whelmed by Betcour · · Score: 1

      I'm not aware of any database that 100% follow the SQL specs. As far as I'm concerned, those are NOT bugs because they behave in a way that is documented, predictable and often convenient. You can dislike that behavior, but it's design choice, not a bug.

      And as such, you don't have to WORK AROUND them - if your application is designed correctly it should checks that integers are the right size, rather than passing values around and waiting for an error to show up later at the storage level (ie too late !). Working around a bug is wasting programming efforts and code lines to do something you shouldn't normally be doing. This is not what you describe here - you should be checking your values before passing them to the database anyway. There's no "work around" to be done.

      Imagine a bug like that popping up in the middle of a bank year, and only being caught several months later. Disaster.

      No one is saying you should run a banking application on MySQL. Or Postgresql or Firebird for that matter.

    6. Re:Under whelmed by Sxooter · · Score: 1

      QUOTE:
      I'm not aware of any database that 100% follow the SQL specs.
      UNQUOTE:

      But, don't you think a database with SQL in it's name might make some small effort to follow the specification? Nah, I guess not.

      But the real issue is that data coherency is the job of the database, not the code that sits on top. While there may be dozens of pieces of code that touch a database, there is only one small point of entry, the database. relying on code to make sure your data is coherent is suicide.

      --

      --- It is not the things we do which we regret the most, but the things which we don't do.
  38. e.g. JDBC by lonesometrainer · · Score: 1

    They have a nice type-3 (100% java) jdbc driver available.

    why not take a look at their homepage?

  39. Re:SQL not relational by the0ther · · Score: 2, Informative

    This is utter nonsense. I see the author's argument but it is incorrect and pedantic. In nearly all cases duplicate records are not returned. When I say "nearly all" the exceptions are: tables without a primary key containing otherwise duplicate rows, and the results of multiple SELECT statements using the "UNION ALL" keyword. UNION ALL tells the engine to go ahead and give me ALL of the rows including duplicates.

  40. Don't Forget the Other Firebird by jazman_777 · · Score: 1
    This product is not to be confused with newly renamed Firefox web browser, which was also called Firebird for some time.

    And it is not to be confused with the Pontiac Firebird automobile, which was popular for a while but now discontinued. They do make a Sunfire now, which is not to be confused with Firefox, a web browser, which used to be called Firebird, which is now a dbms.

    --
    Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
  41. Firebird Documentation by esconsult1 · · Score: 4, Insightful
    When oh when will they make the documentation browsable on the web. Instead you have to download crappy zip files which contain PDF's.

    I think that this reduces uptake of the database, becuase of the barriers to just taking a casual peek of their features. The whole documentation is just locked away with the keys.

    Perhaps this is becuase they want more people to have paid support? A PDF manual is all well and good, but at least give us a bone to chew on with a feature list, reasons why people should use the database and so forth.

  42. Re:ok by Waffle+Iron · · Score: 2, Insightful
    ok, can you give firefox it's old name back? No one knows or cares about your project, but people actually give a fuck about firefox

    Which old name?

    It was once Netscape... until they screwed up in the market so bad that they gave up on it and released the source as:

    Mozilla... until it became so bloated and overdesigned (and dangerously close to a movie company's trademark on a mutant lizard) that they had to start over as a project called:

    Phoenix... which they forgot to check to see if that trademark had been used by a software company for about 20 years already, causing them to have to change it in a kneejerk reaction to:

    Firebird... which they also forgot was already taken by a project that was already smart enough to not use "Phoenix". Thus causing them to switch once again to:

    Firefox... which, (assuming they finally did their homework and checked on trademarks) is actually the best name since the original "Netscape".

  43. And I'm still waiting for... by plopez · · Score: 3, Funny

    the "Bitchin' Camaro Database"... :)

    --
    putting the 'B' in LGBTQ+
  44. Firebird Has a lot of corporate takeup, already by j0keralpha · · Score: 1

    A number of ACCT and Manufacturing packages have already taken up Firebird as a backend. It's being looked seriously as a replacement for Pervasive and some of the other low end/low cost RDBMSs.

  45. Re:SQL not relational by Anonymous Coward · · Score: 1, Insightful

    When I read rants like those contain in Database Debunkings or the hyper-attenuated formalism of C.J. Date's book, a little voice keeps saying "any yet...and yet". Somehow despite the fact that we use tables instead of relvars I can still book a flight or order a book from Amazon. If these guys are selling something other than arrant pendantry somehow it has escaped me and, it seems, the rest of the data processing world. Put up or shut up. If SQL is such a violation of proper set theory and that matters for something, you should be able to make a fortune selling the Tutorial-D's purity of essence

  46. Mod this down as Firebait! Mindless MySql trashing by ArseneLupin · · Score: 0, Redundant
    people who are comparing it to MySql: is mysql a *real*, relational, transactional database server? stored procedures? triggers? foreign keys?

    Mindless MySql bashing troll! Mod down. And for those who for some reason don't know: current MySql versions support all these features.

    Of course, if you go back to the stone age you might find some MySql version which didn't yet support everything that makes a database a database, but if we go that far back in time, I'm sure we'll find flamebox be wanting in some areas as well...

    Oh, [to the moderator who modded this as Informative]: may I have some of that "tobacco" that you have in your pipe? It smells so good!

  47. next firebird/phoenix/firefox name by Anonymous Coward · · Score: 0

    I think they should they should name it interbase ;-)

  48. Client caching by msobkow · · Score: 5, Insightful

    While Postgres is the better database, installing Firebird/Interbase is a much easier task for the average user. That makes it a terrific little cross-platform client-caching database, such as letting the spreadsheet users slice at the data with an ODBC driver without killing the primary database server. For the same reasons, it's a handy tool for writing small standalone database apps without locking in to a Win32 codebase (e.g. MS Access.) I'd say it even has potential to serve the same kind of markets that the "light" servers like Sybase SQL Anywhere serve.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:Client caching by Anonymous Coward · · Score: 3, Informative

      I use both firebird and postgres almost daily. They are very similar in many ways. Both are easy to install, and administer. Both have support for true database features like foreign keys, triggers, and transactions. Interbase runs well on Windows. Although I don't like using windows as a server the fact that our clients feel like they have a choice between linux and windows has helped us close the deal on a few occasions (advantage Firebird). Postgres is more popular with the OpenSource community and more free software is written for Postgres than for Firebird so if you are setting up open source software for your clients there is probably more free stuff available for Postgres - I suppose that is an advantage for Postgres.

    2. Re:Client caching by rainman_bc · · Score: 1

      I gues you've never installed Postgres on FreeBSD. cd /usr/ports/databases/postgresql73 make install clean And firebird: cd /usr/ports/databases/firebird make install clean Yeah, way easier with Firebird. lol when evaluating a database, it's not important to look at "ease of installation" unless your an IT "pro" who can't follow instructions. And there's a quite few out there...

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    3. Re:Client caching by Anonymous Coward · · Score: 0

      Wow, a bit clumsy aren't you - you missed catching the gp's point by quite a ways.

    4. Re:Client caching by msobkow · · Score: 1

      Having planned, coordinated, and implemented the rollout of Oracle 6, Oracle 7, Sybase 10, Sybase 11, Sybase 12, Sybase SQL Anywhere, Postgres, and DB/2 UDB 5 through 8, on Solaris, AIX, HP-UX, Linux, WinNT, Win2K, and Netware platforms, I think I might be qualified to judge Firebird as an easy client caching installation.

      Client caching means Win32 90% of the time, OS/X on two machines to date, and the rest various *nix workstations. Closest I've been to BSD for servers was SunOS -- only dev databases aren't on SMP hardware.

      --
      I do not fail; I succeed at finding out what does not work.
  49. You misconstrue by Anonymous Coward · · Score: 0

    You make it sound like there was bad blood between the two projects. Mozilla Firebird changed its name not because of impending lawsuits, but because having two Open-Source projects with the same name just makes things *really* confusing. When you google "firebird", which project would you be getting? When you and your friends talk about "firebird", is it a car, a database, or a web browser? When Gentoo... well, you get the idea. Really, the issue isn't what you make it to be.

  50. I think you're wrong by roystgnr · · Score: 4, Informative

    Slashdot reported it when Interbase was first announced to be going open source, and followed up on the actual releases afterward, so lots of people cared a few years ago. Interbase keeps getting mentioned by users in more general database discussions as well, so at least some Slashdot users still care, even users who are more interested in database features than in database names.

  51. Why I know about Firebird by rossjudson · · Score: 4, Informative

    I've used it in several projects, over the years. In my day job, we recently added Firebird to the list of databases that we support as warehouse targets for our application. Firebird's instant installation, small footprint, and portability (a few meg) are good reasons to do this. Another good reason is that it outperforms Oracle on the same hardware, as well as several other commercial databases.

    We used to deploy Interbase as part of a product at a company I worked at years back. We would install, start the system (which had multi-gigabyte databases at times), and then not look at it again for YEARS. Two years could go by without tuning, transaction log clearing, or anything else, for that matter. It doesn't have transaction logs (doesn't need them), and sweeps itself clear of most detritus automatically.

    Backups could effortlessly be done on the fly. Full two-phase commit support. And when it comes to complex transactions, it's one of the best databases out there because of its generational architecture (something it shares with PostgreSQL).

    There are a few rough edges on it, like the lack of a standard GUI administration tool. Java support was slow to evolve. The lack of care given by Borland hurt the product for a time. The Firebird people seem to have done a lot of hard work, and deserve praise.

    And for the record, Firefox or whatever the hell it is calling itself this week is one of the stupidest excuses for a software package I've seen to date. It's Mozilla minus most of the features that make Moz useful and extensible. It doesn't run any faster than Moz in resident mode. It performs no useful function I am aware of. The adulation it receives utterly escapes me; it seems to be a prime example of building software for the past. The engineering effort would have been far better spent on Moz itself.

    1. Re:Why I know about Firebird by CeleronXL · · Score: 4, Interesting

      To each his own. Firefox is definitely faster than the Mozilla Suite, aka Seamonkey. You haven't really used it have you? Firefox not useful and extensible? Are you kidding? With XUL and its extension engine it is incredibly extensible.
      Note that in my comments about FirebirdSQL, I only mentioned the company. I haven't used the database and so I will acknowledge that it may very well be a great database, whereas it would appear that you clearly have not used Fx if you honestly think it's not extensible. And if it is the case that you haven't used it, you can hardly call it a poor excuse for a software package.

      This is obviously going to get modded down as flamebait or trolling, as is always the case on Slashdot when a good debateable topic comes up.

    2. Re:Why I know about Firebird by Green+Light · · Score: 0, Troll
      And for the record, Firefox or whatever the hell it is calling itself this week is one of the stupidest excuses for a software package I've seen to date. It's Mozilla minus most of the features that make Moz useful and extensible. It doesn't run any faster than Moz in resident mode. It performs no useful function I am aware of. The adulation it receives utterly escapes me; it seems to be a prime example of building software for the past. The engineering effort would have been far better spent on Moz itself.
      That has to be one of the most inane statements that I have ever seen on /. (that is, among posts that have not already been moderated as flamebait). It is so wrong that I (as are most rational readers, I'm sure) am absolutely speechless...
      --
      "Send an Instant Karma to me" - Yes
    3. Re:Why I know about Firebird by Anonymous Coward · · Score: 2, Funny

      It is so wrong that I (as are most rational readers, I'm sure) am absolutely speechless...

      Which would explain the lack of actual content in your post.

    4. Re:Why I know about Firebird by Anonymous Coward · · Score: 0

      I was digging your post until the mention of firefox. Then you lost all credibility.

    5. Re:Why I know about Firebird by Anonymous Coward · · Score: 0

      You're a well off-topic.

    6. Re:Why I know about Firebird by Snoopy77 · · Score: 2, Interesting

      From our experience Interbase needs a lot of baby sitting.

      Our databases would be less than a gig but any time it did a sweep it would take up one whole processor and go bye byes for an exteneded period of time. In fairness to Interbase, we were using the Borland Database Engine as well which was a cause for most of our database headaches but I would not recommend Interbase in a large production environment.

      I thought the best thing about Interbase were the GUI admin tools (IBExpert in particular).

      --
      "She's a West Texas girl, just like me" - G.W Bush Iraqis
    7. Re:Why I know about Firebird by rossjudson · · Score: 1

      Since Moz is essentially instantaneous for all operations on my system, I have trouble seeing how a browser based on the same rendering engine is going to be much faster than that.

      I've downloaded and looked at two versions of Firefox. It looks like an interesting exercise that the author has engaged in, but I really don't see the point. As his feature set picks up, he'll find himself pretty much where Moz is.

      I happen to like Moz's integrated news/mail/irc/composer...no reason not to have them, they work just fine, and like I said, speed/mem is simply not an issue any more; at least, not for programs in the Moz family.

      I guess I'll download Firefox again and take a look. Can't say I won't come to the same conclusion, but you never know.

    8. Re:Why I know about Firebird by rossjudson · · Score: 1

      We had bad experiences with BDE as well, and used several mechanisms to communicate. The machines running IB just ran day in, day out for years. Never touched them.

      The sweep problem wasn't something I experienced, but usage patterns differ.

      For anybody who's interested, reading Jim Starkey's comments on the Firebird development lists are great fun. He is a total no-bullshit, pull-no-punches kind of guy, and right about a hell of a lot. Fun to read. Maybe not so fun to receive, especially when you've been trying damn hard to get code done. But fun for the rest of us.

    9. Re:Why I know about Firebird by CeleronXL · · Score: 1

      There's far more to a browser than it's rendering engine. Mozilla had all of its extras, an email client, composer, address book, etc. built right into the same app, which slowed down response time of the program especially at startup. Fx has been stripped of all of that bloat.

    10. Re:Why I know about Firebird by Anonymous Coward · · Score: 0

      Let me get this straight: on YOUR system you can't tell the difference. Let me guess, more than 2 GHz? You're not running on a 1 GHz Duron like some of us are, are you?

      And also, since YOU like the news/mail/irc/composer everyone else must like it too, huh?

      You really should take a look before looking like a jackass again.

      -Another message posted using Mozilla FireBirdFox.

    11. Re:Why I know about Firebird by shadowmas · · Score: 1

      the parent post is very true abt firebird. its a very good database system. its pretty simple to install and manage but has lots of features compared to other opensoucrce database servers.

      its a pity thought that he chose to flame firefox bcuz its also a very good browser the only one which was able to replace internet explorer as the primary browser for me. moz guys made a mistake on choosing the name. but now that they corrected it i think its time to move on. also firebird was already famous before the name dispute.

    12. Re:Why I know about Firebird by james72 · · Score: 1

      One of the main points that Firefox has risen to address is choice. Moz is a fine suite - but wouldn't it be better to split all it's modules out and let people choose what vendors software they use for each function? Love the Moz browser, but want to use a different email client? Why should your system be burdened with Moz's email client if you don't use it? Choice is good.

      I also really liked your Firebird points. I didn't like the Firefox flame on the end of the post...

      -James.

    13. Re:Why I know about Firebird by Anonymous Coward · · Score: 0

      I haven't used Firefox on Windows or Linux but on OS X it's no faster to launch or load pages than Mozilla, and much slower than Safari. Also, it uses Windows-XP style toolbar icons by default in the OS X version. I have to say, I'm not especially impressed either.

    14. Re:Why I know about Firebird by Kent+Recal · · Score: 1

      Firefox is definitely faster than the Mozilla Suite, aka Seamonkey. You haven't really used it have you?

      Well, to me Firefox is just as slow as Mozilla. The renderer is fine speed- and otherwise (it's gecko after all) but the UI on both is based on XUL. XUL is slow.

      IF you want to know what a fast browser really feels like then get yourself a copy of galeon.
      Opinion: It's also using gecko and doing most of the bookmarks, tabs and popup-blocking stuff better (faster!) than moz. So you may consider it a drop-in replacement for bloatzilla.

    15. Re:Why I know about Firebird by CeleronXL · · Score: 0

      Windows users can use K-Meleon which is very stripped down, but Windows only. Hellishly fast.

      XUL is getting faster with each progressive release. A few days ago there were some string changes made in Fx that made everything 3% faster, and we'll be seeing more such string changes in the near future, so Fx 0.9 should be much faster.

      I can't believe one of my posts in this "thread"-type thing was modded as -1, Troll. Clearly done by a FirebirdSQL fan, because it was anything but a troll.

    16. Re:Why I know about Firebird by rossjudson · · Score: 1

      No, jackass. Are you the author of FireWhatever? Yes, AC, my system is behind the times but faster than 2Ghz. You may have noticed that computers are getting faster over time. You may also have noticed that time is moving in a forward direction. This means we are moving TOWARDS the future. Amazing, huh?

      So if computers in the future are going to be faster, and a lot of them already are, why waste engineering time that could be better spent in other areas?

      I don't think very many people like the newsreader in Moz. It works for me. With XUL, someone can tune the one that's in there, or write a brand new one.

      Looking at the bug lists for FF, it's got a long way to go. More power to the guy who writes it -- have at it. But "faster" doesn't cut it as a reason to move away from the Moz baseline and start over.

      "Maintainability" does, though...and that's about the only reason I can see for official engineering time to be put into FF.

      Jackass.

    17. Re:Why I know about Firebird by rossjudson · · Score: 1

      Which part is wrong?

    18. Re:Why I know about Firebird by rossjudson · · Score: 1

      Gotcha. And in resident mode, it doesn't matter. Like I said, it's more or less instantaneous. So setting aside the startup issue (which becomes less important with every passing month), what's the compelling feature?

    19. Re:Why I know about Firebird by rossjudson · · Score: 1

      The flame was a result of being irked by what I consider to be misplaced loyalty to FireFox; while it is an interesting exercise, Firebird/Interbase is serious business, has been around in one form or another for 15 years, and has only started getting architectural competition in the last few years, with Postgres' adoption of a multi-generational record architecture. The casual dismissal of one of the best databases out there (depending on task) over a vanity re-upholstering of Moz gets to me, I guess.

      But you are right...there really wasn't a need for it.

  52. Why Firebird? by Ian+Bicking · · Score: 3, Insightful
    I've worked with Firebird a bit (some software I develop supports it), but I'm not quite sure what it offers over PostgreSQL. It's difficult to work with from an administrative level, and not terribly well documented -- certainly PostgreSQL beats it on these terms. In terms of features they are mostly on par, with PostgreSQL supporting some fancy OO features that most people won't use, and Firebird perhaps having a few small features of its own (though few). PostgreSQL has much more momentum -- in large part because it's a historically open source codebase, and the code reflects that development methodology. It's accessible to outsiders and maintainable. Firebird doesn't have this, and I don't know if it will ever be very accessible. Look what happened to Mozilla... (though OpenOffice maybe is doing better?)

    Then, just to mix things up, you have SAP DB, which is open source with a very proprietary background, much like Firebird. And probably with a lot of the same problems in terms of administration and code accessibility.

    I certainly wish the developers no ill will, or to disparage their efforts -- but I've yet to see the argument for using Firebird outside of legacy projects. It's easy to argue MySQL vs. Firebird, but PostgreSQL is the real competitor.

    1. Re:Why Firebird? by hobuddy · · Score: 3, Informative

      I'm not quite sure what it offers over PostgreSQL.

      • distributed transactions (these are indispensable for reliable distributed object programming (I do a lot))
      • savepoints (elementary form of nested transactions)
      • native Windows support
      • embedded mode (the database engine is capable of running as an in-process library rather than a standalone server)

      It's difficult to work with from an administrative level, and not terribly well documented...

      I agree that the documentation is mediocre, but firmly disagree that it's hard to administer. The key is: don't. Make a couple of changes in the config file if you need to, configure automatic backups, then forget about it.

      --
      Erlang.org: wow
    2. Re:Why Firebird? by egoots · · Score: 2, Informative

      One argument is to run natively on a Windows server. In saying this, I am not recommending Windsows as as server, just pointing out that Firebird/Interbases has good traction and support there.

    3. Re:Why Firebird? by tin_the_fatty · · Score: 1

      I agree that the documentation is mediocre

      I bought the media kit for Borland Interbase, and the big box contains a couple of CD and a few inches thick of documentation. (I never dug too deeply into those, but that's another story) When you said "mediocre" were you referring to the free documentation or were you referring to documentation of Firebird/Interbase as a whole?

  53. Why do Linux downloads have 686 in name? by Anonymous Coward · · Score: 1, Interesting

    The Firebird Linux download section is titled 386 but the files have 686 in their name. Can I install these on less than a 686? Namely an AMD K6-2/550mhz ?

    Firebird-linux-i386 [show only this package]
    1.5.0-Release [show only this release]
    FirebirdCS-1.5.0.4290-0.i686.rpm
    283788 6 0 i386 .rpm
    FirebirdCS-1.5.0.4290-0.i686.tar.gz
    2802184 0 i386 .gz
    etc...

    1. Re:Why do Linux downloads have 686 in name? by KoopaTroopa · · Score: 1

      I thought that the K6 series was compatible with all the Intel "686" stuff.

      Not that that answers why either the section or the files are mislabeled.

      --
      Sharpies don't just sniff themselves.
    2. Re:Why do Linux downloads have 686 in name? by Ice_Balrog · · Score: 1

      The AMD K6-2's are 686's. So, yes, you can install it on your box.

      --
      #include "sig.h"
    3. Re:Why do Linux downloads have 686 in name? by Anonymous Coward · · Score: 0

      Every newgroup discussion I've found and read searching on
      "AMD K6-2" 586 686
      says your wrong, that an AMD K6-2 is actually only a 586. Many of these threads were specifically talking about Linux rpms too.

      So again my question, does this mean no Firebird 1.5 for AMD K6-2? Why are filenames with 686 in them, under a section titled "386"?

      I have faster workstations in the house (AMD Thunderbirds - 686), but I've relegated my older K6-2s for use as servers for in-house use and for skill development (SAMBA, NFS, CVS, Tomcat, Apache, etc). I would assume others with home networks would to.

      This is a mistake IMHO. Borland a perfect example that as a corporate Systems Engineer, I've always seen Delphi for example loose out because companies don't want to go with it of there aren't a lot of skilled developers with those skills. And your going to have less people developing Firebird skills if you limit the field of PCs it can run on.

  54. Re:ok by Hamster+Of+Death · · Score: 1

    So now hopefully it won't be confused with the movie of the same name.

    Firefox

  55. Love It! by rixstep · · Score: 0, Redundant

    I've always been a big fan of the Foxbird Database system, and this release looks better than ever!

  56. Re:Mod this down as Firebait! Mindless MySql trash by __past__ · · Score: 2, Informative

    With "current MySql versions", you mean the pre-alpha development release which for example will have (potentially crude) stored procedures? As opposed to the current unsupported beta version, which is the first to finally have subqueries (of course, after years of telling customers that you don't want them anyway, just as MySQL AB did with all other basic DBMS features they only now promise to support in a few years)?

  57. Shipping a product? Firebird is your friend by siberian · · Score: 2, Interesting

    We are about to ship a cross platform Struts (java) based application and needed a simple, low maintenance, low overhead, cross-platform,truly free and fast sql engine.

    Enter Firebird. Installation is a breeze under both operating systems and its all plug and play after that.

    MySQL is nice but can be a maintenance headache and good luck included it in a shipping product, it violates the license or so the lawyers tell me.

    I use mysql on my webservers, I embed firebird in my shipping products. Its been great so far!

    1. Re:Shipping a product? Firebird is your friend by droleary · · Score: 1

      We are about to ship a cross platform Struts (java) based application and needed a simple, low maintenance, low overhead, cross-platform,truly free and fast sql engine.

      It's probably too late for you, but other's making the same choice might also want to consider SQLite.

    2. Re:Shipping a product? Firebird is your friend by OYAHHH · · Score: 1

      I,

      Totally agree. I'm doing almost exactly the same thing and Firebird is the easiest package of them all to configure.

      Plus, I've used Interbase for over 10 years now and I've NEVER had a data corruption.

      --
      Caution: Contents under pressure
  58. Hmm, not quite ... by zonix · · Score: 2, Informative

    It was once Netscape... until they screwed up in the market so bad that they gave up on it and released the source as:

    Mozilla... until it became so bloated and overdesigned (and dangerously close to a movie company's trademark on a mutant lizard) that they had to start over as a project called:

    That's a bit harsh - how about unfair competition? Anyway, "Mozilla" was the internal codename for Navigator at Netscape. It has always been it's name and it still is today (now for the whole suite).

    To quote the "Freeing the Source: The Story of Mozilla " :

    Mozilla was a term initially created by Jamie Zawinsky and company during the development of Navigator. The team was working at a similarly frantic pace to create a beast vastly more powerful than Mosaic, and the word became the official code name for Navigator.

    Firefox... which, (assuming they finally did their homework and checked on trademarks) is actually the best name since the original "Netscape".

    They better! The name is catchy and the logo is quite beautiful. Try "Help" > "About Mozilla Firefox".

    z
    --
    What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    1. Re:Hmm, not quite ... by vadim_t · · Score: 1

      I checked the about screen.

      Why does a program called FireFox have a logo that's a (nice looking) FireBird? I was expecting to see the fox from here instead.

    2. Re:Hmm, not quite ... by zonix · · Score: 1

      What build are you using? Mine is "Gecko/20040207 Firefox/0.8" - it's a fox, alright. In more than one sense actually. :-)

      z
      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    3. Re:Hmm, not quite ... by vadim_t · · Score: 1

      Gecko/20040219 Firefox/0.8

      Maybe there's something screwed up in the gentoo package.

  59. ditto by kpharmer · · Score: 1

    This isn't static data functionality - it's standard data warehousing functionality.

    And none of the open source databases have yet caught up with the features that the commercial databases have been adding over the past seven years in support of this.

    Still, I've used postgresql for some reporting, and it isn't the end of the world to drop back to older technology in warehousing. But the lack of materialized views isn't the real issue - it's the lack of any form of partitioning.

    1. Re:ditto by bwt · · Score: 1

      Actually, I consider materialized views both an OLTP and a warehouseing feature of Oracle, because you can sometimes completely avoid the need to build a separate warehouse by using materialized views directly in your transaction server. Because of query rewrite, you can retroactively add them and not have to do rewrite all your SQL. The MV just acts like a steroid enhanced index. You can do this while not having to introduce data latency from a scheduled extraction process that supplies the warehouse.

      I certainly agree that partitioning is another feature that can be make or break for a high end project.

      There are a whole host of other features that Oracle has that nobody else even comes close: function based indexes, index organized tables and advanced queueing, wait based monitoring, very good execution plan selection plus fine grained optimizer hint overrides, etc., etc., etc...

    2. Re:ditto by bucknuggets · · Score: 1

      You're right - materialized views are pretty useful in OLTP as well. Though I only use them when desperate - since i prefer to do more transformations on data than can be easily done with the MV. > There are a whole host of other features that Oracle has that nobody else even comes close: > function based indexes, index organized tables and advanced queueing, wait based monitoring, very > good execution plan selection plus fine grained optimizer hint overrides, etc., etc., etc... DB2 seems to be coming along pretty nicely with its 8.1 version. I'm building a warehouse with it right now - and its multi-dimensional clustering combined with partitioning across multiple machines results in a very fast system. The only thing I miss from oracle is transportable tablespaces, but with my reload strategy it isn't a killer. Haven't tried teradata - I assume that product line is pretty good as well. But there's a huge gulf between the open source solutions, sql-server and the databases that can manage terrabytes of data.

    3. Re:ditto by Arioch_BDV · · Score: 1

      Yaffil (hance i think Firbird too) has function-based and expression-based indices. Same as SubSelects in COMPUTED BY columns. But sure, in each of Oracle, DB2 and MS SQL, one may find a *set* of features that no one else provides. They are leaders, that's so.

  60. Genuinely interested & thwarted.... by im+a+fucking+coward · · Score: 2, Interesting

    The documentation on the sight is dated / plagued:

    "Last 10 Releases"

    31-Dec-1969 firebird 1.5.0-Release (Source) ...

    1969? That's a neat trick. Hopefully development is a little more dedicated than documentation.

    Looking at the list of who's deploying the DB on which platforms, the organization list is impressive, but where's current information?
    "This page was last updated on 2000-12-31 21:23:04 -0400" doesn't impart warm fuziness, nor do the few references to Linux kernel 2.2.x.

    Who's managing the project, and why do they suck at advocating it?

    1. Re:Genuinely interested & thwarted.... by Anonymous Coward · · Score: 0

      that's probably the reason why few people had heard of them before the mozilla naming issue came up.

  61. Re:SQL not relational by MattRog · · Score: 4, Informative
    You are only considering SELECT * cases.

    Obviously you can generate duplicate rows any number of ways if you include non-unique column combinations in your SELECT.

    In any rate, because SQL allows you to create a table *without* a primary key (which then means that result sets can have duplicate rows) then it is not relational. End of story.

    No one is saying that SQL is double-plus ungood, just pointing out that it is not relational (just as saying that 2+2 != 5, and the sky is not made of fish), and don't attribute deficiencies of SQL to deficiencies of the relational model.

    You can begin to understand how Date and Pascal et al at DBDebunk.com feel if you consider the following scenario (this thought exercise presupposes that perfect is possible):

    You spend a lot of time and effort developing The Perfect Car which is perfect in every way. Not only does it not require any non-renewable resources, but it drives to any destination perfectly and is perfectly safe. You work out all the mathematical details and proofs and can say: "I have proven that this car is perfect."

    Since you do not have the time/expertise/money/etc. to build The Perfect Car you then license your Perfect Car Model to the big automakers. They then proceed to implement your Perfect Model in the form of a "Perfect Car" Implementation. Unfortunately for them, building The Perfect Car is very, very difficult, almost impossible. The automakers then proceed to make significant changes to your Perfect Model. They cut corners, make changes which violate certain precepts and assumptions in your Perfect Model, etc.

    They then put The Less-Than-Perfect Car on the market but proceed to call it a Perfect Car. After the "Perfect Car" Implementations that people start to buy get lost, run out of gas, and even blow up and kill them, they start saying: "These Things are wrong with the Perfect Car!"

    Enterprising people then decide to try and fix the "Perfect Car" Implementations by creating New Perfect Car Models. Some of these models include the implementations as a background. Some create Entirely New Models Without Significant Scientific Background. They provide, possibly, incremental improvement over the "Perfect Car" Implementations but generally include just as many, if not more so, opportunities for flaming, burning death as the current Implementations. Not only that, but they throw out Actual Working Parts of the "Perfect Car" Implementations!!

    And all the while you are there, yelling from the sidelines: "But that is not a Perfect Car! I have shown you the path (Model) to building the Perfect Car! I have Proved it True! If you'd stop wasting your time on these other Stupid Designs and focus on the Perfect Model then we'd all be better off!"


    Now that this long-winded description is over you can replace The Perfect Car with The Relational Model and "Perfect Car" Implementations with {Oracle, MySQL, etc.}. You can replace "New Perfect Car Models" (including "Without Significant Scientific Background") with {XML, OO-DBMS, 'Persistence Layers', etc.}.

    No one is saying that you cannot use SQL products or XML, or that you cannot accomplish tasks in these tools, just that when used in the context of data management they are poorly solving what the Relational Model already solved.

    Because IT practitioners are poorly educated and increasingly fad-driven they latch onto non-solutions (like XML, "Post-Relational", OO-DBMS, etc.) and put little or no pressure on DBMS vendors to get it right. Even worse, if someone does release a Truly Relational DBMS there are no guarantees that anyone will buy it due to the ignorance of the IT community.

    Put simply: People don't know what they're missing, so they don't know to ask.
    --

    Thanks,
    --
    Matt
  62. Re:SQL not relational by MattRog · · Score: 2, Informative

    RowIDs typically are:
    1) Not visible to the user
    2) Based on physical (e.g. on-disk) row placement (e.g. Oracle's ROWID pseudocolumn)

    Both of these are violations of the relational model.

    If, however, every table had a unique sequence number or something, then sure they would not be materially in breach of the uniqueness constraint. However, remember that result sets are *also* relations so you would have to have DISTINCT appended to every SELECT statement to also pass the uniqueness test.

    --

    Thanks,
    --
    Matt
  63. One version, many numbers by IMSoP · · Score: 1

    Is is just me, or is it kind of daft to declare that
    "Firebird 1.5 is the first release of the Firebird 2 codebase"

    I mean, if it's Firebird 2, call it Firebird 2, for crying out loud!
    It reminds me of Sun, and their wonderful numbering "system" for Java:

    "At the second JavaOne conference, Sun will announce version 1.4 of Java 2 Enterprise Edition, along with version 1.4.1 of Java 2 Standard Edition and JavaBeans version 2.9"
    [Not a real quote, but close enough...]

    1. Re:One version, many numbers by Anonymous Coward · · Score: 0

      In the example you give, 1.4.0 is the version of the J2EE SDK (a specific implementation of the language specification), while the 2 refers to the version of the language itself.

      Confusing? Yeah, a bit, but if you pay attention, it's over in about ten seconds.

    2. Re:One version, many numbers by IMSoP · · Score: 1

      But the point is, why use numbers at all if you're not going to use them consistently? If it's Java v.2, then you should implement it using the Java SDK v.2.x And if you don't like starting new software at version 2, don't call the new version "2"! It's not like numbers are the only way of distinguishing a new version of something - how about:

      • letters - A,B,...
      • too boring? Alpha and Beta have established meaning with software, but how about Aleph, Beth, etc. They sound cool.
      • meaningful suffixes - like "32" for a 32-bit rewrite. That way, people can use your suffix on their derivatives, even if they didn't have a previous version. (Like the early Win32 apps having "32" in their names).
      • arbitrary suffixes - an acronym for Next Generation, or New Technology, perhaps. That way, you can even carry on working on both codebases if you want to (a la "Windows NT"). Not to mention "Windows 98 S.E."
      • codenames - just pick a cool-sounding word, and use that to distinguish. Do Intel have the Pentium 4, version 5? No, they have the Pentium 4 Prescott.
    3. Re:One version, many numbers by Arioch_BDV · · Score: 1

      :-)
      You've forgotten dates, just like Windows 95 or latest snapshots of www.IBExpert.com

  64. Re:For those of you hung up on the whole name issu by DrEasy · · Score: 1

    My GF suggests Browzilla... (I won't dare suggest any name on the Firefox forum, they're getting very touchy about the subject!)

    --
    "In our tactical decisions, we are operating contrary to our strategic interest."
  65. Doesn't google have its own database? by Stone316 · · Score: 1

    As far as I know google uses its own proprietory software not mysql.

    --
    "Thanks to the remote control I have the attention span of a gerbil."
    1. Re:Doesn't google have its own database? by ThogScully · · Score: 1

      I recall reading that they used MySQL, though they had their own search and indexing built around it. Looking through their job opportunities listings, most mention that MySQL experience is a big plus.
      -N

      --
      I've nothing to say here...
  66. Mod parent up. by mmcguigan · · Score: 1

    Where are the moderator points when you need them?

  67. LOCKSMITH? by csk_1975 · · Score: 1

    Does this new version still use "LOCKSMITH" for the backdoor password? Or has it been changed to something else?

    1. Re:LOCKSMITH? by Anonymous Coward · · Score: 1, Informative

      Of course not.

      The bug was found by us, and the release of it publicly was done, initiated by us, through CERT. http://www.cert.org

      Updated versions and patches were availabe before the public release of the security bug.

      Cheers

      Mark

  68. Re:MOD PARENT UP by Anonymous Coward · · Score: 0

    Ah shit, I commented on this while logged in. Fuckers.

  69. In that case, by PigeonGB · · Score: 1

    yeah, that's really dumb of them.

    --
    I have 3656.9 Bogomips. How many Bogomips do you have?
  70. Re:SQL not relational by scosol · · Score: 1

    Not if you use the hidden BACKDOOR!

    --
    I browse at +5 Flamebait- moderation for all or moderation for none.
  71. amen by Anonymous Coward · · Score: 0

    I love Firebird, it is very nice to the DBA and throws errors when you insert invalid data or data that gets truncated.

  72. So.... by cookiepus · · Score: 1

    Does it handle mailto tags or what?

  73. To Lazy to parse the license by mikeabbott420 · · Score: 1

    can I use this in a comercial system? who do I pay what does it cost? I am learning python because it seems unencumbered. I am certainly willing (HAPPY) to contribute back any bugfix or enhancement I might need for my own use, (it would be a huge ego thing if I could contribute to a usefull open source project) The key thing is can I use it the "consulting-ware" for definition see http://www.joelonsoftware.com/news/20020507.html stuff I make my living from.

    --
    This program was made possible by a grant from the Ultra-Humanite, and viewers like you.
    1. Re:To Lazy to parse the license by Anonymous Coward · · Score: 0

      can I use this in a comercial system? who do I pay what does it cost?

      The license is essentially similar to that of Mozilla. You can use it in a commercial environment without paying anyone, although there is commercial support available for IBPhoenix if you need it.

      Furthermore, there's a feature-complete and free Python driver for Firebird here

      .
  74. Version??? by brunes69 · · Score: 1
    Development on the Firebird 2 codebase began early in Firebird 1 development, with the porting of the Firebird 1 C code to C++ and the first major code-cleaning. Firebird 1.5 is the first release of the Firebird 2 codebase.

    Someone care to translate? What's the damn version? 1? 1.5? 2? How can 1.5 be a release on the 2.0 codebase??

    I am lost.

    1. Re:Version??? by egoots · · Score: 1

      Someone care to translate? What's the damn version? 1? 1.5? 2? How can 1.5 be a release on the 2.0 codebase??

      As I understand it,

      Firebird 1.0x - this is based on the Interbase 6.0 open source release with numerous bug fixes. applied. This codebase was written in C.

      Firebird 1.5 - is just released. The codebase was largely rewritten in C++. In addition it contains many new features and optimizations. This is sometimes referred to as the "Firebird 2" codebase.

      Firebird 2.0 - development is underway. Amongst other development additions, Jim Starkey (original architect of Interbase) has also been contracted to do a tru 64 bit port to Sparc and AMD platforms.

    2. Re:Version??? by Arioch_BDV · · Score: 1

      agree.
      Consider it same way as GIMP2, which development unbstable branch is still numbered for 1.x

  75. Re:Firebird/fox by cbreaker · · Score: 1

    Great! Then you owe me $699 for a license* to use Slashdot!

    * binary only. no html or javascript. I am sympathetic to the problem you face caused by me.

    --
    - It's not the Macs I hate. It's Digg users. -
  76. Why you're modded +3 Flamebait by Anonymous Coward · · Score: 0

    And for the record, Firefox or whatever the hell it is calling itself this week is one of the stupidest excuses for a software package I've seen to date. It's Mozilla minus most of the features that make Moz useful and extensible. It doesn't run any faster than Moz in resident mode. It performs no useful function I am aware of. The adulation it receives utterly escapes me; it seems to be a prime example of building software for the past. The engineering effort would have been far better spent on Moz itself.

    This little statement makes me wonder if I should even trust any of the things you said before it.

    Firefox is definitely faster. It has some features that Mozilla doesn't have, and all the good features of Mozilla. Anything else you need can be added through extensions, but I've never had to do this. It IS the next Mozilla, Mozilla in its current state is obsolete.

  77. Toy is getting there by fferreres · · Score: 1

    I know it's a toy, but it's getting there eventually. MySQL already has nested subqueries, both in the WHERE or FROM parts. I am not sure they allow them to be in the SELECT portion, but that really important (can't you always simulate it if you are allowd to use them in the FROM part?).

    Stored procedures and triggers are already in beta (i know, but that means they will be usable sooner), transactions are already there and work fine. They will stabilize.

    This is a marginal benefit for very large companies but an incredible bonus and fresh air for small and medium companies. The free factor is making small and medium companies more profitable, taking away some of the benefits of being a monster company (ie: minimun size to be able to be profitable in a given business).

    MySQL, Postgre or Firebird are suitable for 95% of the jobs IMHO.

    --
    unfinished: (adj.)
  78. Re:Firebird/fox by Anonymous Coward · · Score: 0

    Quote from this article

    Despite the new name being approved by AOL Legal, supporters of the FirebirdSQL database were quick to object (though the name is also used by many other people).

    So was AOL Legal wrong?

  79. Re:Firebird/fox by Anonymous Coward · · Score: 0

    was just reading through old comments on the subject and found this comment to be particularly interesting.

  80. Re:SQL not relational by Anonymous Coward · · Score: 0

    Okay, now riddle me this: If the theoretical relational model solves real problems that the real-world relational databases don't, then why don't the RDBMS vendors change their products? Or why hasn't any newly developed RDBMS, ever since the advent of the relational model in the 1970's, chosen to implement the "proper" relational model instead of the "crippled" one? Can you give an example of a real-world problem that is solved better by the theoretical model than the model implemented by RDBMS systems?

  81. Enlighten me... What is MySQL missing? by Man+In+Black · · Score: 1

    All of the stuff that MySQL lacked (and still lacks in usable form)

    Alright, I'm somewhat of a beginner as far as databases are concerned. I've only really used MySQL, and admittedly, I've only used it for relatively small tasks so far... but what is it that MySQL lacks? Are there actual tasks that simply can't be done (I've noticed people saying InnoDB apparently helps), or is it just a matter of performance and efficiency? Are these important things that are missing, or just specialized features that I probably won't even need unless I'm dealing with monster, multi-gigabyte corporate databases?

    And if MySQL is supposedly missing a bunch of stuff... then why are people still using it? Are there things it does better than the rest of the DB's out there?

    I don't mean to start any DB Wars or anything... I'm legitimately curious here. The only reason I chose MySQL in the first place was because I needed a DB, and I recognized the name, and so far, it's done everything I've needed it to do... so unless someone can inform me of some crazy-amazing feature I'm missing out on, or can show me something that seriously outperforms MySQL (I'm running on a very slow system by today's standards), then I doubt I'll stop using MySQL anytime soon.

    --
    -"One machine can do the work of fifty ordinary men. No machine can do the work of one extraordinary man." -EH
    1. Re:Enlighten me... What is MySQL missing? by joeykiller · · Score: 3, Informative
      MySQL is very easy to set up, relatively easy to configure and well documented. Most of the time all you need to do is to save som tabular/spreadsheet like data and do some queries on them. In these cases MySQL rocks (I use MySQL a lot), and its fast as well.

      There's a lot of examples of what MySQL can't do, but I'll just give two. Let's say you want to do this:
      SELECT word FROM dictionary WHERE id IN (SELECT word_id FROM article WHERE article_id = 1)
      This SELECT gets all words used in an article, and looks them up in a dictionary. You can't do this in MySQL.

      What you can do in the latest alpha versions is this:
      SELECT word FROM dictionary WHERE id = (SELECT word_id FROM article WHERE article_id = 1)
      But this will only return one row, so it's not the same. Other DB systems will also let you create functions inside the database, which can be reused later.

      Another thing you can't do with MySQL is set up DOMAINs (or constraints); with Postgres you can specify that a field in a table should be an integer, but only integers between (for instance) 1 and 1,000,000.

      And it's a lot more. But admittedly most people won't be needing the advanced functions a lot, if at all, so if MySQL suits your need just use it. Databases are a little like other tools: You use the one that's best suited for the job.
    2. Re:Enlighten me... What is MySQL missing? by Arioch_BDV · · Score: 1

      "SELECT word FROM dictionary WHERE id IN (SELECT word_id FROM article WHERE article_id = 1)"

      That is not good for Interbase-clones, it is treated like "WHERE (id = word_id_1) or (id = word_id_2) or..."

      The better way is
      SELECT word FROM dictionary WHERE EXISTS( SELECT * FROM article WHERE (article_id = 1) AND (word_id = id))

      I think even mySQL is capable of that :-)

      PS: Bill Todd made a comparision of MySQL vs Interbase, and while there is a load of Borland PR, it has correct points. Sorry, have no URL under fingertips, but there is link on www.IBPhoenix.com

  82. Re:SQL not relational by leandrod · · Score: 1
    > why don't the RDBMS vendors change their products?

    First, they are not RDBMS vendors. They are SQL (or quasi-SQL, as with Oracle and MySQL) DBMS (or quasi-DBMS, as with MySQL again) vendors.

    Now, answers are easy. You might as well ask why it took Apple 20 years to have a real OS, or why MS don't have security at all. Do you want it spelled out? Ignorance, they are too rich, lazyness, and shoot-the-messenger, NIH mentalities.

    > why hasn't any newly developed RDBMS, ever since the advent of the relational model in the 1970's, chosen to implement the "proper" relational model

    Just take a look at my own Relational DBMS implementations list at DMoz. Not all listed there are truly relational, but the best approximations at their own time. You can even get free downloads. None is SQL compliant.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  83. Re:SQL not relational by leandrod · · Score: 2, Informative
    > we should trust that web site as authoritative

    That is one thing you should never do. Never ever trust any web site as authoritative.

    What could be good for you is to read the arguments critically, and think. Perhaps even get a book, either on you library or buying it -- Date's _An Introduction to Database Systems_ *is* the standard reference textbook in the area, so it's worth it.

    BTW, all caps in a title is perfectly accepted practice.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  84. Re:SQL not relational by leandrod · · Score: 1
    > the exceptions are: tables without a primary key containing otherwise duplicate rows, and the results of multiple SELECT statements using the "UNION ALL" keyword

    Anyway these are not sets, therefore not relations.

    How'd ya feel if I invented an algebra where almost always gave a number as a result?

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  85. Relational != SQL by Anonymous Coward · · Score: 1, Informative

    More insightful information on the differences between SQL-DBMS and R-DBMS is on DB Debunk
    OT: Have to post AC, have been modding.

    1. Re: Relational != SQL by Anonymous Coward · · Score: 0

      Damn, lost my mod points anyway. Posting AC does not help.

  86. Do you know/use Borland Delphi? by andika · · Score: 1

    If you use Borland Delphi (a Pascal-like language and development environment under Windows), then naturally you use Interbase for its RDBMS server. Then when you want to deploy that system and you need a dedicated database server, you can easily install Interbase on Win or Linux, or even better (IMO), Firebird instead.

  87. Re:Firebird/fox by finkployd · · Score: 1

    So was AOL Legal wrong?

    Legally? probably not. Ignoring the lawyers though, this kind of namespace collision should be avoided in the OSS community just as a matter of principle. People get confused as it is knowing what program to use for what.

    Finkployd

  88. Re:Firebird/fox by Anonymous Coward · · Score: 0

    Good point. But then wouldn't the fault be placed onto FirebirdDB? What I don't understand is that if they valued brand recognition as much as they have demostrated during the naming debate, why did they even choose the name "Firebird" in the first place? The name is very, very common and you didn't need to google it up to recognize that.

    Mozilla obviously wanted a web browser codename that sound cool (e.g. phoenix, firebird, firefox). I would gander that FirebirdDB choose "firebird" for similar reasons. If they wanted to be uniquely identified, shouldn't they have choosen a different name?

    I guess it just seems (from my point of view mind you) that it was poor strategic planning on the part of FirebirdDB. Not saying if it was appropriate for Mozilla to take up that name after learning of FirebirdDB, but didn't FirebirdDB bring this onto themselves?

  89. Re:Mod this down as Firebait! Mindless MySql trash by Anonymous Coward · · Score: 0
    How could parent possibly get moderated as Informative. Hey, you're pre-alpha versions are 3 years old, and this has been in production since ages. Since long enough that certain distributions, such as SuSE even ship the features within their MySql Rpm.

    Hey, just because you chose to live under a rock for 3 years doesn't mean the time stood still for everybody else too!

  90. There are bugs in Interbase 6.0 by Arioch_BDV · · Score: 1

    You're lucky!!!
    I started development for Intebase 5.1 and in a month i found 2 bugs, one of them made database unable to restore from backup. Just a specific order fo creating tables.
    Dummy finding bugs, how would You like it?

    And had You heard of merge of Firebird and Yaffil projects. Why... Some points are told in 'in the beginning' post. To continue it:
    Later some developers from both teams were pricking themselves in russian Interbase usergroup.
    Firebird was enhancing SQL, making Yaffil re-implement those features.
    While Yaffil was too much faster, making Firebird team try to optimise their codebase.
    It was a neverending reason of jokes.

    And sure they were finding and fixing bugs. Each in their own codebase, with only limited help to each other.
    By the way, Yaffil, and later in 1.5alpha Firebird too, had changed heap manager - and found reasons of 'Interbase is unstable under heavy load' rumours. There were place, where memory was freed, but still used after.

    This spring 2 awfull bugs was discovered, one of them existed in Interbase 4.1 and maybe even longer back to the history.
    There was legal way to make duplicate values in P.K.
    It is amazing that no one stepped upon that 2 rooks ever before.
    That was the last drops, working together on fixes the teams finally decided to merge back.
    It will be interesting and, i hope, great story.

    PS: i wonder if You will look through Firebird issue tracker, and try those bugs over Borland Interbase, wat will there be the result ?

    PPS: Have Your heard of www.ibaid.com ? Alas, interbase _can_ crash the database.
    For early IB6.0x it was enougth to grow database file 4gb of size, the next bytes were written into header :-(
    Small office never needed such amounts of data, but will they - they will certainly need mature DBA that knows about the issue.

  91. ...in the beginning by Arioch_BDV · · Score: 1

    Borland developed Interbase for years, and suddenly... Suddenly they tld they are no more interested in Interbase, so the project is discontinued.
    there worst thing about commercial apps, is that once You may hear 'game over'.
    The developers was shocked and even organised some movement to force Borland notto harry killinh Interbase. Thanks to www.mers.com

    In about a year Borland reacted, telling here is You Interbase 6.0 - if You like it - take it and do whatever needed. Later they acted back with IB 6.5, but that is out of iinterest here.
    They has been taken - by developers who resigned from Borland after that, especially those, who resigned from Digital many years ago to create the database, as Digital's chiefs were not interested in enhancing OpenVMS OS built-in database management.
    Sure during this year they found themself a work and could not soent too much time on cleaning ex-IB6 code.
    So the next year was spent for creating the community and finding sponsors.
    This 2 years delay was so dark time, that 2 programmers in SaintPetersburg forked the stalled Firebird project and started Yaffil project (http://yaffil.ibase.ru, seems the fastest but Win32-only clone of Interbase)

    Later there appeared new developers, some grants, fund, et cetera. But those two years were defenitely years of death.
    Personally i treat 'Firebird' as sardonic codename, meant "We're still here after those years, are we dead or not?"

    Currently, when life is back in Firebird, and after they together fixed some awfull legacy bugs, they desided to merge together again, but theis is another story... :-)

    1. Re:...in the beginning by Anonymous Coward · · Score: 0

      OK, so I now understand why they named the project Firebird. But doesn't my point still stand? They chose "Firebird" because it related to their situation and it sounded cool (that's the exact same reason Mozilla had picked the name). But, they still picked a very common name nevertheless. They shound have recognized the possibility that another software project that did another type of task (e.g. web browsing) would come around eventually. If they were going to be so picky on excluding the name from being used by other software projects (it was only a codename for crying out loud), then perhaps they should have picked something more unique?

      The way i see it is this: FirebirdDB chose the name "Firebird" even though there already existed several software projects with that name. Later on, they denounce Mozilla for doing the same. Whether or not those previous projects were very active should not be a determinant on whether you take on another project's name or not.

      My take: FirebirdDB had every right to take on the name Firebird. But Mozilla also has that same right as well. I feel FirebirdDB was being inconsistent in their line of reasoning and judgement. One of those "You can't have your cake and eat it too" situations. I feel they made a mistake, but I have never heard anyone of their representatives come out and recognize that fact. It is unfortunate really.

  92. Ha! Do You really think it is easy ? by Arioch_BDV · · Score: 1

    ..as soon as someone will create one.
    Those PDF's that are on their homepage (http://firebirdsql.org/) are taken form Borland. You can distibute and read them but cannot change a single bit in them.

    You see, nothing is locked.
    Opposite, Helen Borrie (hope i did not misspelled) created the book on Firebird that is going to be published, do not know how detailed it is.
    Year ago russian usergroup created a book too (most efforts was from developers of www.devrace.com), though it is more like 'getting started', things You must know, and things You must be interested and searching beyond this book for particular kinds of work you need done.
    Maybe You can read of that book at www.interbase-world.com, though it may appear - since no interest to the book was shown aside Russia - it may be omitted on English pages.

    Aaahh! shame on me, i forgotten. 3 years ago a book in Germany was published.

    Yopu see, 3 books it is not 'nothing'.

    So why there is no documentation?
    Simple. Try to make one *without* reading those PDF's and any derived from them information....
    Can anyone do it?

    That is like the disclamer at www.DotGNU.org that tells You never read any documentation, that has some license restriction, if You want to participate - cause after all Your work may be used to issue the whole project as pirated one.

  93. date was wrong by Arioch_BDV · · Score: 1

    Time is flying fast...
    Not this spring, sure, but the last fall.
    Merge was announced in December.

    I remember those troubles was between winter and summer and...
    Sorry, seems i am too longing for March :-)

  94. We use COBOL (Delta actually) by Anonymous Coward · · Score: 0

    .. and our systems are based around it. Online, Batch and Web Interface (through CICS). It's not that bad actually.

    When you're next dealing with a database (DB2 in this case) with over 20 million rows in the main table, your other table (address) is 16 times the size and you need create a program for updating data according to rigid criteria consider Delta (which generates COBOL code). I could do this in Java, C, C++ or indeed any language that runs on the mainframe (yes, Java runs on OS/390).. but COBOL (Delta :) ) is designed for it. Wheeee

  95. Re:Mod this down as Firebait! Mindless MySql trash by __past__ · · Score: 1
    MySQL 5 will be the first version to include stored procedures, according to MySQL AB. It is hardly 3 three old, and everyone using a release labeled "Preview" on the vendors homepage "in production" must be insane or have taken the clichee that MySQL users don't care much about their data too serious.

  96. Re:SQL not relational by nial-in-a-box · · Score: 1
    But is there actually a need for a truly relational database? Granted, there are a lot of people out there creating databases and apps on top of them who don't really know what they're doing, but that is beside the point. Just because an inexperienced programmer could more quickly create a useful, reliable app in AppleScript than in C++ does not suggest that C++ is wrong. OK, so this is a poor comparison, but the point is that either way you need to grasp database design fundamentals to make a good, solid database.

    Not to get really pissy here, especially since my reply is somewhat tardy, but your statement "In any rate, because SQL allows you to create a table *without* a primary key (which then means that result sets can have duplicate rows) then it is not relational. End of story." is complete garbage. Relational does not refer to restrictions that the software imposes on the developer. Any database product that allows a developer to relate a record in one table to a record in another table is relational. "End of story." I can whip up a shitty Python app that satisfies this definition in a few minutes, and just because it isn't a ROFLSTFUIANALIMHODBMS doesn't mean it's not relational. Relational is an idea. Please try to understand that. I don't know where you get your ideas from, but you seem to have a sadly anal (and incorrectly so) way of looking at this. The first real thing I learned about databases was the difference between single-table, flat-file databases and multi-table, relational databases. Can you honestly tell me that what I do for a living is not develop relational databases just because you have such a narrow definition? I do not mean to offend, but I cannot let your statement stand uncorrected. I also apologize for using an "end of story" line in any way, as there often isn't anything definitive about computers or software.

    --
    I am feeling fat and sassy
  97. Re:SQL not relational by MattRog · · Score: 1
    But is there actually a need for a truly relational database?

    Only like there is actually a need for a car that doesn't crash and drives you to your destination. Certainly you can get from point A to point B with any old auto now -- but it would be easier and safer if the car did that for you (presupposing that such algorithms could be written etc.)

    Relational does not refer to restrictions that the software imposes on the developer.

    The Relational Model is quite well-defined by Codd -- your assertions are quite false and make little or no sense. A series of "rules of thumbs" is available online - search google for Codd's 12 rules.

    Any database product that allows a developer to relate a record in one table to a record in another table is relational. "End of story."

    You are incorrect. A RDBMS is comprised of relations which have a very strict mathematical definition. Their set-theoretic background rules out duplicate tuples (rows) - sets do not contain duplicates. A relation that allows duplicates is no longer a relation by definition, therefore a DBMS which allows duplicate rows is not relational. Q.E.D.

    Can you honestly tell me that what I do for a living is not develop relational databases...

    You can logically model a RDBMS - but no such product exists to fully implement that logical model. You have to shoehorn it into a SQL DBMS which does not fully implement the relational model.

    Try picking up a few good books/papers (Practical Issues in Database Management by Pascal, just about any of Codd's works, etc.) and reading them. You are obviously ignorant about RDBMS.
    --

    Thanks,
    --
    Matt