Matthew Stanfield said:
Usually, i'll use "enum('0','1')" in place of a boolean type.
> well. The only annoying thing I can think of, from a programming
> perspective, is MySQL's lack of a Boolean type - the manual says use
> TINYINT(1) which works fine but is slightly annoying because of the
> extra type conversion needed every time you use it. Apparently MySQL
> will be implementing the Boolean type soon in accordance with whatever
> SQL standard requires it. Quite why it still has not been implemented,
> even though MySQL is into version 4, I have no idea - as a programmer I
> find this a staggering omission but presumably they have their reasons
> and perhaps most people are happy with TINYINT(1), but for clarity of
> code TINYINT(1) is inferior to a Boolean type.
> I hope this helps,
> Jerry Apfelbaum wrote:
>> I have been tasked with evaluating open source databases for a large
>> upcoming project: e-commerce, B2B, high availability.
>> The O/S is most likely to be Linux, although FreeBSD could possibly be
>> used (lower probability).
>> So far, it seems that MySQL, MaxDB, PostgreSQL, and Interbase/Firebird
>> are possible candidates.
>> Does anyone know why we should or should not use any of these? Does
>> anyone know of other possibilities?
>> Id very much appreciate hearing your comments and recommendations.
>> I have only recently started these evaluations. BTW, my own
>> background is from the Oracle DBA world.
>> MySQL is certainly popular and seems to have very good performance,
>> but I am concerned that the lack of Triggers, Stored Procedures,
>> User-Defined Functions, and Views (to a lesser degree ) will be a
>> MaxDB "appears" to be more feature-rich and possibly more
>> industrial-strength. How does its performance and stability compare
>> to the others?
>> Many Thanks.
>> Jerry Apfelbaum
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1