This error has been really annoying me tonight!
I have an app that uses Embedded Firebird for its DB so that I don’t need to
install a DB server. On Vista my app throws an exception “Error trying to
write to file (the correct path here)”.
Now we have 64bit builds of Firebird 2.1 for MacOSX 10.5, we have issues trying to test them properly using the Firebird QMTest QA suite. This QA suite relies on Python and kinterbasdb. Currently Philippe Makowski has been able to run the tests from a 64bit Linux client. But is unable to run the tests locally. Well currently the python framework that comes with MacOSX 10.5 is only 32bit and this forces a 32bit build of kinterbasdb, since the build environment of kinterbasdb uses distutils to use the same compile switches as python. So I thought I would have a look at the issue and see if I could build a 64bit version of kinterbasdb for MacOSX 10.5.
This is how I did it…
An introductory article about using the new Generic Database Output Module
This modules supports a large number of database systems via libdbi. Libdbi abstracts the database layer and provides drivers for many systems. Drivers are available via the libdbi-drivers project. As of this writing, the following drivers are available:
Rsyslog is an enhanced multi-threaded syslogd. Among other features, it offers support for on-demand disk buffering, reliable syslog over TCP, writing to MySQL and PostgreSQL databases, fully configurable output formats (including great timestamps), the ability to filter on any part of the syslog message, and on-the-wire message compression. It is designed as a drop-in replacement for stock syslogd and thus is able to work with the same configuration file syntax. Of course, some enhanced features require changing the configuration file, but in general, this should be fairly easy.
Release focus: Major feature enhancements
This week I looked at Firebird2 and decided to give it a try. In a few minutes I discovered that the package libqt4-sql (the one that provides support for accessing databases from Qt4 apps) comes with just a few drivers enabled (coincidentally the ones that I mentioned above). Firebird is NOT enabled by default.
Here is how it was solved
I’m pleased to announce the 0.10.0b2 release of SQLObject.
What is SQLObject
=================
SQLObject is an object-relational mapper. Your database tables are described
as classes, and rows are instances of those classes. SQLObject is meant to be
easy to use and quick to get started with.
We’re getting the current batch of new stuff out the door, with plenty
more waiting to fill into the next trunk. Theres a broad variety of
new things here which are summarized below.
Download SQLA 0.4.3 at: http://www.sqlalchemy.org/download.html
Full changes:http://article.gmane.org/gmane.comp.python.sqlalchemy.user/11726/
I’ve been messing around with Django for a while now and having fun. It reminded me of why and how I got started in this field.
[ED:There is an nice firebird mention ]
Using Apache, Webware and Firebird as the database I set out to build something.
Firebird? Yes anything to avoid the MySQL bandwagon. I couldn’t say for sure now, but at the time Firebird was far superior to MySQL. The Firebird team didn’t think that ACID properties, foreign key constraints, stored procedures etc. were just some esoteric optional extras for something with pretensions to being an RDBMS.
Firebird .NET provider has ability to create parameterized queries. Both named and unnamed parameters are supported. Everything works as you expect with select, insert, delete or update commands. The tricky part comes with stored procedures. Unlike MS SQL, that has direct support for named parameters, in provider, we’re parsing parameter names and we’re sending it to server “in right order”, so developer doesn’t need to know, that internally parameters were send unnamed.
A how-to style article about FBExport (in spanish).
