I am trying to choose between postgre and firebird databasses. The database will be installed on a windows 2003 server with asp.net 3.5. i don't want to use sql server because of price issues and I don't want MySQL I had a bad experience with it and the .net connector and the membership provider.
相关问题
- Carriage Return (ASCII chr 13) is missing from tex
- How to store image outside of the website's ro
- 'System.Threading.ThreadAbortException' in
- NOT DISTINCT query in mySQL
- Request.PathInfo issues and XSS attacks
Firebird + FreeadhocUDFs + IBExpert, and just programming.
we have 2 systems in production for 6 years (20 domains, 200 tables, 50 views, 370 stored procedures, 600 triggers, 205 generators, 11, roles, etc, etc) and have been tested to migrate to PostgreSQL (only test, we love Firebird).
In tables with traditional data types (integer, varchar, date, numeric, etc, etc.) differences could be for one or the other, as appropriate, but in stored procedures, Firebird is much more powerful than Postgresql, much more simple and elegant.
Two or three years, any Linux distribution, not including Firebird, only Mysql and Postgresl. Not for nothing today, but tradicionesles distributions (ubunutu / opensuse / fedora / centos, etc, etc) and Firebird include in their repositories.
Postgresql do not say that is worse than Firebird, Firebird is not that much better than Postgresql. But without hesitation I say that Firebird has nothing to envy to Postgresql, and in many ways is more powerful.
(sorry for my bad english)
Why don't you try SQL Express a scaled down version of SQL from Microsoft which is free to use.
Most of the features are the same on both however I recommend Firebird 1. FB - supports multiple collation within a table 2. FB - more choices on mature drivers to work with 3. FB - connection managed by either Thread or Process depend on your use/setup 4. FB - embedded support
Not recommend Stay away MS SQLExpress
A little Draw back 1. FB - blob handling is not so great if condition below are true but if you move blob column(s) into separated table, then no issue with blob a. massive data mining/manipulating b. blob column(s) is/are defined with other data columns
They are both cool. However, one BIG advantage for Firebird is it's .net data provider. Good mature solution, vs buggy npgsql (or some paid Postgres drivers). So it it mostly to chose what db you are more familiar with or what are your developement team skills.
Both Postgres and Firebird are excellent databases.
I always worked with Firebird since 2005 writing application in Delphi, C# and ASP.NET. I never had a corrupt database in my projects. I never needed to work with another database. Why Firebird instead of PostgreSQL? Because Firebird is:
Well. If you are using Firebird you dont need another Database. :)
I've always been impressed with Postgres; it's traditionally had a more complete feature set (in terms of ACID compliance, support for advanced queries, etc.) than MySQL, it has solid Windows ODBC drivers, and its documentation scrupulously points out any areas in which it deviates from the SQL standard. (All databases, it seems, deviate in one respect or another, but Postgres is the only one I've seen that makes sure you know when you're doing so.) I haven't tried the usage scenario you describe, but I've had no problems running it on Linux and accessing it from both Windows ODBC and Linux clients.
I don't have any experience with Firebird; sorry.