<<O>>  Difference Topic InterBase (r1.4 - 22 Nov 2003 - KirkStrauser)
Changed:
<
<		 I posted the following comment to SlashDot one day. I think it pretty well sums up my feelings for InterBase:
>
>		 I posted the following comment to SlashDot one day. I think it pretty well sums up my feelings for InterBase:

Line: 18 to 18

 It may be good in theory, and I'm sure that some people like it. For us, however, Interbase is completely undependable and just barely usable for routine tasks.

-- KirkStrauser - 13 Nov 2001

Added:
>
>
META TOPICMOVED KirkStrauser? date="1069521457" from="Main.InterBase" to="Computing.InterBase"
 <<O>>  Difference Topic InterBase (r1.3 - 20 Aug 2002 - KirkStrauser)

 I posted the following comment to SlashDot one day. I think it pretty well sums up my feelings for InterBase:

Line: 18 to 18

 It may be good in theory, and I'm sure that some people like it. For us, however, Interbase is completely undependable and just barely usable for routine tasks.

-- KirkStrauser - 13 Nov 2001

Deleted:
<
<

(Poop on Yoop and don't tell!)

 <<O>>  Difference Topic InterBase (r1.2 - 20 Mar 2002 - AaronCMeadows)

 I posted the following comment to SlashDot one day. I think it pretty well sums up my feelings for InterBase:

Line: 17 to 18

 It may be good in theory, and I'm sure that some people like it. For us, however, Interbase is completely undependable and just barely usable for routine tasks.

-- KirkStrauser - 13 Nov 2001

Added:
>
>

(Poop on Yoop and don't tell!)

 <<O>>  Difference Topic InterBase (r1.1 - 13 Nov 2001 - KirkStrauser)
Line: 1 to 1
Added:
>
>		 I posted the following comment to SlashDot one day. I think it pretty well sums up my feelings for InterBase:

My company is currently trying to decide between MySQL? and PostgreSQL?, with the latter being the likely choose.

We're currently using Interbase, and I have to say that it's the biggest pile of fetid horror I've ever had the displeasure of having to maintain. Why?

  • First off, you have to specify the exact path of the database file on the remote machine. That is, you can't connect to database FOO on host BAR - you have to connect to /var/databases/FOO.gdb. Heaven help you if you ever change your directory layout and run multiple applications against the same server.
  • The command line client, isql, is awful. It has no supports whatsoever for readline-esque features such as command history, or even deleting the previous character. Standard procedure is to type queries in a text editor and then paste them into the isql shell.
  • A nice feature we discovered: suspending the isql client with ^Z will lock the server until you foreground the client process again. We were NOT amused to discover this: "HEY! THE $#!*(@# SERVER IS FROZEN AGAIN! WTF?!?!?"
  • We've experienced several (!!!) cases of database corruption where we were completely unable to recover any data inserted into a database after that point.
  • AFAIK, no equivalent of mysqldump exists for Interbase. At least, I was unable to find one when I critically needed it (see previous point). I eventually hacked one up in Perl that works OK for our needs, but that still rather surprised me. AFAIK (yes, twice in one post! :), you can only back up the binary database to another binary file. BTW, my boss gave me permission to release my backup tool under the GPL. Email me if interested.

The only reason that we're using the much-despised database server is that our rather largish apps are written against it, and it will take a bit of effort to change. Also, given the lack of the SQL dump utility (other than the hack job I put together), getting information from Interbase to anything else is non-trivial.

It may be good in theory, and I'm sure that some people like it. For us, however, Interbase is completely undependable and just barely usable for routine tasks.

-- KirkStrauser - 13 Nov 2001

View topic | Diffs | r1.4 | > | r1.3 | > | r1.2 | More
Revision r1.1 - 13 Nov 2001 - 17:24 - KirkStrauser
Revision r1.4 - 22 Nov 2003 - 17:10 - KirkStrauser