Comparing the performance of several operations in FB2.1, OraXE and SQLServerXE using the vendor specific .NET data access drivers, I discovered Firebird was about 3 times faster than the others which were both nearly the same speed.
You may wonder, how the Entity Framework will map some basic functions (concatenation, average, etc.) from i.e. LINQ or from EntitySQL to functions supported by database and what functions will be “the selected”. Well the answer is easy.
I’m very excited to announce the release of mojoPortal 18.104.22.168
Its available now on the download page.
The main focus of this release is making mojoPortal more attractive, with the addition of 21 good looking new skins for a total of 34 skins now included with mojoPortal. There were also a few minor bug fixes for things reported in the Forums since the last release.
The 3rd part of the Interbase and Firebird Developer’s manual for ADO .Net was published. Examples for DDL queries, metadata schemas and ODBC sequences were presented.
I’m in the extremely lucky situation that I’ve just started a brand new project, in which I can choose technology. A part of the project is to replace an old Web Project written in Delphi 5 ! and a larger part is going to be new. The main bulk of the project is going to as a web application run on portable barcode readers in a production enviroment. Speed is important.
The 2nd part of the Interbase and Firebird Developer’s manual for ADO .Net has published. It describe code generators and Visual Studio 2005/2008 tools.
It gives me great pleasure to announce that NHiberante 2.0 Alpha 1 was released last night and can be downloaded from this location.
We call this alpha, but many of us are using this in production, so we are really certain in its stability. The reason that this is an alpha is that we have made a lot of changes in the last nine months (since the last release), and we want to get more real world experience before we ship this. Recent estimates are of about 100,000 lines of code has changed since the last release.
by jirkaWe’re moving, slowly, step-by-step. And new functionality is coming in view. Just two pictures showing a piece of functionality. Yes, it’s a “LINQ to Firebird”, in fact LINQ to Entites connected to Firebird.
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.
The main purpose of SchemaProber is to provide a lightweight representation of a database schema. It doesn’t do anything except relay information from the database. Here’s the class diagram for SchemaProber