Re: PostgreSQL/FireBird

> The FSF says the MPL is not compatible with the GPL, but, well, the FSF
> generally finds **all** non-GPL licenses incompatible with the GPL (BSD,
> MPL, Apache, etc.). The only truly GPL-compatible license I know of is
> LGPL (and there have been arguments about that). That’s the problem
> with the GPL. You’re not agreeing to open source your code as much as
> you’re agreeing to abide by the FSF’s political beliefs. Political
> lock-in for developers in lieu of vendor lock-in for end-users.

Quite political stuff in a technical posting from somebody apparently
disliking mixing politics and open source, eh?

It's been said a million times by BSD advocats: put one line of code
under GPL and you instantly become a willingless slave of Richard
Stallmans hoards of children-eating communists.

You don't seem to have the slightest idea of how little power the FSF
even has over project initially developed by themselves (gcc etc), let
alone stuff like the linux kernel.

But you still eternally repeat the "one license to bind them all"
conspiracy theory.

Maybe it's time to move to some other lecture. How about "The
Silmarillion", it's quite good as well.

>
>
>
> Compared to SQLite, Firebird has many more features. Firebird **can**
> function as a network server and runs as a separate process instead of a
> C library that gets compiled in your binary. If you want multiple apps
> to access the same data or you want to use ODBC, Firebird can do that
> without the kitchen sink approach of PostgreSQL.

SQLite also has support for ODBC:

http://www.ch-werner.de/sqliteodbc/

>
>
>
> Compared to JetSQL – which I assume is what Access and Exchange use –
> Firebird is cross-platform. I’ve never used it, but I’ve also never
> been impressed with the performance of anything that has used JetSQL
> (Exchange especially).
>
>
>
> --
>
> Brandon Aiken
>
> CS/IT Systems Engineer
>
> ------------------------------------------------------------------------
>
> *From:* Justin Dearing [mailto:zippy1981(at)gmail(dot)com]
> *Sent:* Monday, February 05, 2007 6:29 PM
> *To:* Brandon Aiken
> *Subject:* Re: [GENERAL] PostgreSQL/FireBird
>
>
>
>
>
> On 2/5/07, *Brandon Aiken* <BAiken(at)winemantech(dot)com
> <mailto:BAiken(at)winemantech(dot)com>> wrote:
>
> FireBird is a direct descendant of Borland InterBase 6. Consequently,
> much like Postgres inherited a lot of Ingres's weirdness (most of which
> has since been weeded out or superceeded with standard SQL compliance),
> FireBird is still very much InterBase dialect-compliant. This is also
> why it still uses a modified Mozilla Public License. I know they've
> achieved ANSI SQL-92 compliance, but I don't know how fully compliant
> beyond that they are. PostgreSQL is mostly working on SQL-03 compliance
> AFAICT. Both use MVCC.
>
>
> What does the MPL have to do with Borland InterBase descendance? Borland
> could have chosen any license they wished. Quite frankly I'm quite
> ignorant about the MPLs terms so please enlighten me.
>
>
>
> Interbase was also primarily used for single instance and embedded
> applications, so it's not intended to scale the same way PostgreSQL is.
>
>
> So I guess one should ask how it scales to SQLite and JetSQL, on the
> appropiate lists of course.
>
>
>
> Firebird's design foci are very small memory footprint, ANSI SQL-92
> complaince, multiple dialects that support aging systems, and very low
> administrative requirements. It lack features and scalability compares
> to PG, but does what it does very well.
>
>
>
> Bottom line: PostgreSQL is more mature because it's several years
> older. Firebird is intended for different applications.
>
>
>
> If FireBird is descended from Ingres, aren't they both the same age?
>
>
>
>
> ------------------------------------------------------------------------
> ** LEGAL DISCLAIMER **
> Statements made in this e-mail may or may not reflect the views and
> opinions of Wineman Technology, Inc. or its employees.
>
> This e-mail message and any attachments may contain legally privileged,
> confidential or proprietary information. If you are not the intended
> recipient(s), or the employee or agent responsible for delivery of this
> message to the intended recipient(s), you are hereby notified that any
> dissemination, distribution or copying of this e-mail message is
> strictly prohibited. If you have received this message in error, please
> immediately notify the sender and delete this e-mail message from your
> computer.