Firebird Branch for C++11 support

Adriano dos Santos Fernandes wrote on Firebird-Devel

Hi!

I created a branch for the C++11 usage proposal.

The branch is not for active development, it’s just so others can play,
test and discuss.

The features are described here:
https://github.com/FirebirdSQL/firebird/blob/work/c%2B%2B11/doc/README.modern_cpp.md

I didn’t found explicit mentioning support of the function features per
compiler, but seems very basic feature for lambdas so I put it there.

I tested in clang++ 3.8.0, g++ 5.4.0 and MSVC 14.

Database .NET 19.4 and dbMigration .NET 3.6 released!

Database .NET 19.4 is an innovative, powerful and intuitive multiple database management tool. You can browse/grant objects, design tables, edit rows, run queries, generate scripts, analyze/monitor SQL and import/export/migrate/sync data with a consistent interface. (Full support for Firebird 1.5~3.0+)

For more information please visit http://fishcodelib.com/Database.htm
Free, All-In-One, Portable, Single executable file and Multi-language.


dbMigration .NET 3.6 is a simple, easy and intuitive multiple database migration and data synchronization tool, With it you can easily migrate schema and data between different databases without complicated procedures.

Supported databases: Firebird 1.5~3.0+, PostgreSQL, SQL Server, SQL Azure, LocalDB, MySQL, Oracle, IBM DB2, Informix, HP Vertica, NuoDB, Teradata, Sybase ASE, SQLite, SQLCe, Access, dBase, FoxPro, Excel, ODBC, OLEDB, Text…etc.

For more information please visit http://fishcodelib.com/DBMigration.htm
Free, All-In-One, Portable, and Single executable file.

Are you prepared for Firebird 3?

So, Firebird 3.0.1 is out, and you are planning to move to it. But are you prepared for this task? Migrating to previous versions was usually an easy task, but is this still true for Firebird 3.x? Answer the following questions to know if you are really prepared to move to Firebird 3!

1) Can I connect to a database created in Firebird 2.5, using Firebird 3?

« Hide it

Database Workbench 5.2 released, includes PostgreSQL support

Upscene Productions is proud to announce the availability of the next release of the popular multi-DBMS development tool:

” Database Workbench 5.2.0 “

This release includes new features and useful enhancements, including PostgreSQL support.

Databases challenges

ODBMS Industry Watch recently interviewed Jim Starkey about “Database Challenges and Innovations”. The complete interview can be seen here. Jim invented the MVCC (Multi Version Concurrency Control) model, which is used inĀ Firebird, InterBase and Postgres RDBMS.

Jaybird 3.0.0-alpha-1 release for testing

Jaybird 3.0.0-alpha-1 has been published for testing. We would really appreciate if you could start testing your applications with this version and provide feedback on stability and behavior, but also on the release notes.

Feedback can be sent to the Firebird-java mailinglist or on the issue tracker http://tracker.firebirdsql.org/browse/JDBC.

Jaybird 3.0 is a big change from Jaybird 2.2 and earlier. We have rewritten the entire low-level implementation to be able to support protocol improvements in newer Firebird versions, made changes with a stricter interpretation of the JDBC requirements, and removed some parts that were either obsolete or not functioning correctly.

We recommend that you do not consider Jaybird 3.0 a drop-in replacement for Jaybird 2.2, and study the release notes carefully.

See:

Jaybird 3.0 Alpha 1 is available from Maven central:

Groupid: org.firebirdsql.jdbc,
Artifactid: jaybird-jdkXX (where XX is 17 or 18).
Version: 3.0.0-alpha-1

For example:

<dependency>
     <groupId>org.firebirdsql.jdbc</groupId>
     <artifactId>jaybird-jdk18</artifactId>
     <version>3.0.0-alpha-1</version>
</dependency>

If your application is deployed to a Java EE application server, you will need to exclude the javax.resource:connector-api dependency, and add it as a provided dependency:

<dependency>
     <groupId>org.firebirdsql.jdbc</groupId>
     <artifactId>jaybird-jdk18</artifactId>
     <version>3.0.0-alpha-1</version>
     <exclusions>
         <exclusion>
             <groupId>javax.resource</groupId>
             <artifactId>connector-api</artifactId>
         </exclusion>
     </exclusions>
</dependency>
<dependency>
     <groupId>javax.resource</groupId>
     <artifactId>connector-api</artifactId>
     <version>1.5</version>
     <scope>provided</scope>
</dependency>

If you want to use Type 2 support (native, local or embedded), you need to explicitly include JNA 4.2.2 as a dependency:

<dependency>
     <groupId>net.java.dev.jna</groupId>
     <artifactId>jna</artifactId>
     <version>4.2.2</version>
</dependency>
1 4 5 6 7 8 15