With new functions in FB 2.1 extracting week of year is supported (based on ISO-8601). So this past article is more simple to do with the new syntax :
extract(week from some_date_field)
.:(firebird):..:(databases):..:(sql):.
Friday, April 25, 2008
Thursday, April 24, 2008
wordpress for firebird
i wonder if i can apply pdo patches to the wordpress 2.5
and maybe after that make it work with firebird later
(pdo is suported by other databases too)
ps:why wordpress team ignores the rest of the world ?
.:(firebird):..:(databases):..:(sql):.
Wednesday, April 23, 2008
firebird + genotoo blog post
LINQ To Dataset DBNull problem
I've got a connection to a Firebird Database.
I've linked DataSources in the IDE. I've got all my 8 tables from which I can retrieve data.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3222905&SiteID=1
.:(firebird):..:(databases):..:(sql):.
I've linked DataSources in the IDE. I've got all my 8 tables from which I can retrieve data.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3222905&SiteID=1
.:(firebird):..:(databases):..:(sql):.
Sunday, April 13, 2008
phpBB 3.0.1 released
phpBB 3.0.1 has just been released, this means some small bug fixes, which were of course necessary in order to ensure the continuous stable release rate of phpBB. The official release topic is posted below.
.:(firebird):..:(databases):..:(sql):.
.:(firebird):..:(databases):..:(sql):.
OpenDBX 1.3.7 released
Release focus: Major bugfixes
Changes:
Many improvements and bugfixes are included in this release and it's recommended to all developers to upgrade to the latest version. The existing odbx_result_free() is deprecated in favor of the new odbx_result_finish(). Additionally, the C++ Stmt::bind() method of the API was removed and the Stmt::escape() method was moved to the connection object. It's now also possible to write data into large objects using the Firebird and Oracle backends, but the Oracle LOB implementation doesn't work at the moment.
.:(firebird):..:(databases):..:(sql):.
Wednesday, April 09, 2008
We went with Firebird 2.0 because
Quote from firebird-general
Yes. We were evaluating various embedded engines a few years ago,
including Firebird, MSSQL XP, Oracle XP, DB2 XP, MySQL, SQL Lite, MS
Access and PostgreSQL. In addition to standard SQL capabilities, our
application required us to be able to mimic the behaviour of other
database engines we support fairly closely.
We went with Firebird 2.0 because:
- Smallest footprint.
- File based databases.
- Lack of size restrictions.
- Friendly license terms.
- Extensive set of data types (with domains to handle anything
funky we run into later)
- Extensive set of collations
- Extensibility
- Active and responsive development community
- Easy installation.
- Easy configuration
- Standards compliance
Limitations we ran into:
- Database files must be local
- Collations are all case sensitive ( we may be able to deal with
this in 2.1, but my 2.0 attempts all failed)
- No built in functions to speak of required a third party UDF
library (this has changed in 2.1)
- No session scoped (i.e. local) temporary tables (global temps are
in 2.1 but not local)
- Different instances of the application cannot both access the
same database file.
The limitations were fairly minor and easy to work around. In
general we are extremely happy with our choice!
Incidentally, our reasons for rejecting MS-SQL XP were:
- Forces our users to install .NET (this was the big show stopper)
- Relatively largish footprint (60Mb if memory serves)
- 2GB database size restriction (this made us nervous as we have no
control over the user's data)
- Missing data types (DATE, TIME)
HTH,
________________________________________________________
Richard Wesley Senior Software Developer Tableau
Software
Visit: http://www.trytableau.com/now.html
.:(firebird):..:(databases):..:(sql):..:(mssql):..:(mysql):..:(postgresql):..:(oracle):.
Yes. We were evaluating various embedded engines a few years ago,
including Firebird, MSSQL XP, Oracle XP, DB2 XP, MySQL, SQL Lite, MS
Access and PostgreSQL. In addition to standard SQL capabilities, our
application required us to be able to mimic the behaviour of other
database engines we support fairly closely.
We went with Firebird 2.0 because:
- Smallest footprint.
- File based databases.
- Lack of size restrictions.
- Friendly license terms.
- Extensive set of data types (with domains to handle anything
funky we run into later)
- Extensive set of collations
- Extensibility
- Active and responsive development community
- Easy installation.
- Easy configuration
- Standards compliance
Limitations we ran into:
- Database files must be local
- Collations are all case sensitive ( we may be able to deal with
this in 2.1, but my 2.0 attempts all failed)
- No built in functions to speak of required a third party UDF
library (this has changed in 2.1)
- No session scoped (i.e. local) temporary tables (global temps are
in 2.1 but not local)
- Different instances of the application cannot both access the
same database file.
The limitations were fairly minor and easy to work around. In
general we are extremely happy with our choice!
Incidentally, our reasons for rejecting MS-SQL XP were:
- Forces our users to install .NET (this was the big show stopper)
- Relatively largish footprint (60Mb if memory serves)
- 2GB database size restriction (this made us nervous as we have no
control over the user's data)
- Missing data types (DATE, TIME)
HTH,
________________________________________________________
Richard Wesley Senior Software Developer Tableau
Software
Visit: http://www.trytableau.com/now.html
.:(firebird):..:(databases):..:(sql):..:(mssql):..:(mysql):..:(postgresql):..:(oracle):.
Tuesday, April 01, 2008
Firebird Project Releases Firebird 2.1 Zeta 2
The Firebird Project today officially releases
the much-anticipated version 2.1 Zeta 2 of its
open source Firebird relational database software
The 2.1 release has many interesting new features that you can play
with, like database triggers, temporary and monitoring tables, common
table expressions, recursive queries and dozens of new inbuilt
functions. We encourage you to see what you can achieve with these new
features and let us know about any deficiency.
Windows ,MacOSX ,Linux kits fir 32-bit and 64-bit
platforms are ready to download now
You are invited to test it furiously
and report your experiences (good or bad) back to the firebird-devel list.
It brings with it a large collection of long-awaited enhancements that significantly improve performance, security and support for international languages and realise some desirable new SQL language features. Under the surface, it also provides a much more robust code platform from which the re-architecting planned for Firebird 2.5/3.0 is proceeding.
The Firebird project roadmap for 2008 is now available.
.:(firebird):..:(databases):..:(sql):.
the much-anticipated version 2.1 Zeta 2 of its
open source Firebird relational database software
The 2.1 release has many interesting new features that you can play
with, like database triggers, temporary and monitoring tables, common
table expressions, recursive queries and dozens of new inbuilt
functions. We encourage you to see what you can achieve with these new
features and let us know about any deficiency.
Windows
platforms are ready to download now
You are invited to test it furiously
and report your experiences (good or bad) back to the firebird-devel list.
It brings with it a large collection of long-awaited enhancements that significantly improve performance, security and support for international languages and realise some desirable new SQL language features. Under the surface, it also provides a much more robust code platform from which the re-architecting planned for Firebird 2.5/3.0 is proceeding.
The Firebird project roadmap for 2008 is now available.
.:(firebird):..:(databases):..:(sql):.
Subscribe to:
Posts (Atom)