Shared page cache ready to be commited in firebird 3.0

Vlad Khorsun wrote about the Shared page cache implementation in 3.0 :
After more than a year of development, testing, switching on another tasks and returning back i’m ready to commit shared page cache implementation into trunk.
I consider it stable enough to be committed into SVN. It runs some stability tests more than 10 hours for longest run and many shorter runs at different configurations.
Here i want to do overview of changes, what was tested, what was not, and what
is work in progress.

You can read more about Shared page cache in the Firebird 3.0 presentation
Update:Feature commited into trunk

Tips:How to Identify if your run 64 bits of Firebird engine

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



 

Amazon’s EC2 Micro Instance and Firebird

Jiří Činčura Blogged about his impression on Amazon’s microinstance :

Few months ago I was playing with different VPS providers and I was also considering deploying the application to some “small instance” cloud. I came to Micro Instance of Amazon EC2. Part of the solution I was doing research for is Firebird database and because the pricing looks good, I tried to install Firebird (2.5 SuperClassic) on this instance.

TURBU – The Ultimate Rpg BUilder is switching to Firebird as storage mechanism

From the about box :

TURBU is an RPG-building engine currently under development. It is being written by Mason Wheeler, and will be able to create and edit RPGs with a wide variety of customizable options, including importing existing project from RPG Maker 2000 and 2003.

And here is the blog post and the message With several advantages listed

I’ve added a bunch of new Event Builder editors, plus music-playing capabilities, but probably the biggest change is to the project database. I’m changing the storage mechanism from the old, built-in file format to a Firebird database.

New Flamerobin snapshot revision 2105 in #debian unstable

You can download and install the package directly from debian sid (tested and works on ubuntu natty too )
http://packages.debian.org/sid/flamerobin
ChangeLog:
-New upstream SVN snapshot : revision 2105
-If main window close event can be vetoed then loop through all other BaseFrame instances and check whether they veto the closing (check for open transactions, unsaved changes to files, active background work and so on). Replaces the previous confirmation dialog that was always shown.
-Store last selected authentication mode for database creation as selection index of the choice control instead of string selection because the entries are translatable strings
-Correct value of ExecuteSqlFrame status bar pane with database connection info restored
-LogTextControl modified to be read-only, custom context menu implemented for selecting, copying and clearing the content
-Regression fixed: parameter data type weren’t shown in procedure property pages any more

pyfirebirdsql 0.4.1 – pure python driver released

pyfirebirdsql 0.4.1: pure python dbapi for firebird rdbms released new version  with these changes:
-Python 2.5 support
-connect() dsn can set port number. ex) dsn=’example.com/3050:foo.fdb’
You read in the full commit log
Hajime Nakagami commented on firebird-python:

The most important reason to supoort Python2.5 is “Jython”.
Now 0.4.1 work on CPython 2.5+(include 3.x), IronPython and Jython.

I have never test on PyPy

1 125 126 127 128 129 200