Content not direct related to FB, but interesting reading.
The django-firebird trunk was updated with new version. It supports django 1.2 and I hope what support the next 1.3 release too.
I was using this version on production web app and all work fine for
now.[ED:also firebirdsql.ro works ok with it]
The prior django-firebird implementation with support for django 1.1 was tagged
Please, feel free to check it out and report any issue.
Any feedback is wellcome.
The forum post with the results are in Spanish but here are the results and translation in English:
1. The computer was as below :
2. Hard Drives :
a. Western Digital 1TB 64MB Cache Sata III Black
b. Crucial 128GB RealSSD C300
The test consisted in the creation of a database with 1 table :
CREATE TABLE COR_PRUEBA (
INTEGER INTEGER NOT NULL,
CHARACTER CHAR (20),
CARACTER2 CHAR (10),
“DOUBLE” DECIMAL (15, 2),
INTEGER1 INTEGER);
ALTER TABLE COR_PRUEBA
PK_COR_PRUEBA ADD CONSTRAINT PRIMARY KEY (INT);
The test is done with the IBExpert 2009.08.19 and consisted of the insertion of 500,000 records (Insert operations) with random data.
Results:
Disc A (HDD): 1hr 11m 40s 43ms
Disc B (SSD): 3m 42s 224ms
What really stunned me was the Big difference and both tests were performed with exactly the same parameters.
Judge yourself whether it is worth mounting a SSD for storage xD.
Here is the guide on installing Firebird 2.5 from FreeBSD 8.1 Ports and creating your first test database.
The article now is on howtoforge.com , please retweet 😉
Seems that the bug CORE-3302 is triggered when there are millions of rows and only in firebird 2.5 and 3.0 (Bug is already fixed in svn)
What you can learn from the bug is the usage of list,distinct,case,extract weekday in the same query
First i have created the query to extract the day in string format from current date
select
list(case extract(weekday from CURRENT_DATE) when 0 then 'Sun' when 1 then 'Mon' when 2 then 'Tue' when 3 then 'Wed' when 4 then 'Thu' when 5 then 'Fri' when 6 then 'Sat' end)
from RDB$DATABASE
In my case the result was Fri.
Then you can create a table with different dates:
CREATE table tasks
(
DATE_OF_TASK DATE
);
Populate the table
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-07');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-07');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-07');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-06');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-06');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-06');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-08');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-08');
INSERT INTO TASKS (DATE_OF_TASK) VALUES ('2011-01-08');
Then start to run the query
select
list(distinct case extract(weekday from date_of_task) when 0 then 'Sun' when 1 then 'Mon' when 2 then 'Tue' when 3 then 'Wed' when 4 then 'Thu' when 5 then 'Fri' when 6 then 'Sat' end)
from tasks
Result should be:
Fri,Sat,Thu
After the new year eve i wanted to test the new boolean columns in the new build that added them for firebird 3.0 , so i have created the columns and then inserted some random bool vaules for test after that i have started to test the bool expressions (and , or …) in a select from the new bool values.
ps: the select worked in isql-fb only , in flamerobin the datatype is not implemented yet (default from ubuntu 0.9.2)
Here is my story about migrating one app from django 1.1.x to 1.2.x using firebird-django 1.2 branch
ISQL has an “add” command to interactively insert records in a table.
Syntax is “add table_name” then it asks for values of each field
More about this command on Firebird-Devel list
Dimitry Yemanov wrote about the complete Firebird 2.5 reference and how will be structured
I’m starting working on the contents for the complete Firebird 2.5
Language Reference with a hope to have it completed this winter. All the
appropriate questions and issues will be posted here in order to keep
everybody in sync. The first thing to discuss would be the document
structure.Here is what I have in mind:
http://www.firebirdsql.org/download/rabbits/dimitr/LangRef.html
It’s just a draft and any feedback is welcome.
The major difference from what we have now is that the syntax diagrams
(along with the detailed description of the every clause) is moved to
the appendix A.The major chapters contain the introduction to the appropriate
statements and the information on how to apply them to the common usage
patters instead.
Hello All Firebirders!
Today we start very important activity – building Firebird Case Studies catalog.
WHAT IS CASE STUDY?
Case study is an example of real-world implementation of certain product.
Case study should be very specific and describe:
WHY FIREBIRD PROJECT NEEDS YOUR CASE STUDIES?
The Open Source Firebird (IBPhoenix) ODBC driver has been updated to Version 2.0 Release Candidate 2.
Alexander Potapchenko wrote on firebird-odbc list:
I resume development of the ODBC driver. The primary goal to finish ODBC
driver 2.0 (with full x64 support and fixed “blocker” level problems) now.
If you are having any problems with the current driver but have not
reported them because the sub-project wasn’t active, then to add them to
the Bag tracker now.
ps: if you don’t know what is the bag tracker 🙂 it’s Firebird Project’s bug tracker.
