Content not direct related to FB, but interesting reading.
Hi FreePascal and Firebird people here is my question
Cross-posted to the freepascal list and Firebird Development mailing lists
Would it be possible and desirable to have FreePascal as an embedded
stored procedure/trigger language in some future release of Firebird? (I
can’t recall this having been brought up before, so I just start the
ball rolling).
Since Intebase 6 release of the source code, Firebird created a lot of changes and additions to the engine.
The only updates that we see today, are small references for new or changed features for specific version.
Further more, the time has changed, and wiki, and other format of documentation should also be in place, including the ability of users to comment and even share how to things in the proper page.
So what do you think on this ?
Working both with Firebird SQL and PDO (but not yet at the same time) I am interested in the combination of both.
According to the documentation the extension is still in experimental status, but I was still curious about how far it has progressed. I decided to redo the experiments Lorenzo Alberton did in an article in 2006.
I performed these tests on PHP Version 5.3.6 with Firebird 2.5 on a Windows 7 machine.
At work we use a lot of Firebird databases, and so far our system admins checked the availability of a Firebird Database by simply trying to connect via telnet to the port 3050 and see if they would get a response. With this kind of check you can’t really determine if the database is really up and running,
Therefore they asked me if I could write a plugin for nagios which would do a real check to ensure that the Databases are up and running, here is my result.
I chose to write the plugin in python, due it’s simplicity, and because I already wrote some script using the python-kinterbasdb extension
Jiri wrote on his blog :
I recently improved the command logging in ADO.NET provider for Firebird. Let me start with little bit of history and then you’ll see the motivation and current improvements.
From Alexey Kovyazin:
Hello All,
Current data transfer from old site to the new site is almost complete. There are following areas in process:
- In Development – QA, Documentations for developers and .NET/Python drivers
- Old news – we will transfer old news for a while, now at 2009-2008 level.
- In About Firebird -> Features description, is in progress
- Grantee reports from old years
- Some minor content adjustments
Also we need to manage setup for daily snapshot uploads.
For regular site updates, like adding news or new FF members/sponsors, dedicated person from DQTeam will manage data adding/changing, until other site contributors will learn how to use CMS.
Actual transfer and redevelopment is almost over, now web-site redevelopment is about “intellectual” re-writing and new content creatiion.
Such process will be run constantly, and there will be always gap between ideal site and good-enough site.
I ask everyone to join the action now, look through the site thoroughly, and then provide actual help in order to jump over gap and switch to the new site in the next few days, and then go to the Phase 2 – improvements and extensions.
Old site will be live for a while, of course, so no content will be missed.Regards,
Alexey Kovyazin
Question: I have a requirement to Identify whether a Firebird system is 64 bit or not,in order to know whether to deploy a 64 bit UDF or a 32 bit UDF. Is there any thing to give the correct information?
The best Answer: Identify this information this way:
fbsvcmgr service_mgr -user sysdba -password masterke -info_server_version -info_implementation
see the manual for more : http://firebirdsql.org/rlsnotesh/rlsnotes210.html#rnfb210-util-svcs
On ubuntu/debian 64 will give :
fbsvcmgr service_mgr -user sysdba -password masterke -info_implementation | grep 64
Server implementation: Firebird/linux AMD64
or you can count if the 64 string is present with -c in grep (notice that there is no need for username and password)
fbsvcmgr service_mgr -info_implementation | grep -c 64
1
One of the biggest tasks for the long-awaited Firebird 3.0 release is the Shared Page Cache feature. With this feature, Firebird will finally be able to fully benefit of SMP machines without having to work with individual cache for every connection.
Vlad Khorsun had been busy working on this, and judging by recent commits to SoundForge, the task is almost finished. Part of the code came from Vulcan. He hopes that people will help doing lots of tests when the first alpha release appears.
Note: Up to now, Shared Cache was only available in the SuperServer model, but SS is not optimized for SMP.
