Discuss Firebird Rc6 Released in the Firebird SQL Development forum on Dev Shed. Firebird Rc6 Released Firebird SQL Development forum discussing administration, Firebird SQL syntax, or other Firebird SQL-related topics. Firebird is the evolution of Borland's Interbase product.
The ASP Free website provides in-depth information on the latest developer tools available from Microsoft. Our cadre of writers, highly experienced industry experts, reveals the best ways to use established technologies as well as new and emerging technologies. Our coverage of Microsoft's development and administration technologies is among the most respected in the IT industry today.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month! Download and Activate to enter!
Intel® Graphics Performance Analyzers is a powerful tool suite for analyzing and optimizing your games, media, and graphics-intensive applications. Used by some of the best developers on the planet, Intel GPA lets you maximize your app’s performance.
Posts: 303
Time spent in forums: 1 Day 6 h 45 m 28 sec
Reputation Power: 21
What changed in this version :
- fixed minor inconsistencies in charsets naming.
- GSTAT crash in some switch combinations.
- Fixed broken savepoint handling in BREAK/LEAVE/EXIT.
- Fixed optimizer : Prefer single indices instead of composite ones,Prefer full-match unique indices.
- enhancements to win32 instreg / instsvc install tools.
Fixed RC5 bugs:
- BREAK/LEAVE incompatibility with FOR EXECUTE STATEMENT loops
- Bug with expressions without fields inside aggregate-functions.
- EXECUTE STATEMENT returning BLOB datatype.
- Various issues with server-side database aliases. In particular, restore support for relative paths in local connection strings
- Possibly incorrect stream mapping in DSQL parser
- Make COALESCE/CASE output descriptor more SQL-standard.
- Engine crash during execution of DDL altering long recursive procedure->trigger chains
- Thread-safety issues in the SS client library and Windows CS listener process
- Engine crashes if IO error happens early during database startup in SS builds
- Maximum number of indices per table increased
1) Old maximum number of indices was 64, new max value is (DB_PAGE_SIZE/16)-2
2) When actual number of indices for a particular table exceeds 256 engine behavior may be unstable
Posts: 8,526
Time spent in forums: 3 Months 1 Week 1 Day 3 h 1 m 2 sec
Reputation Power: 534
Hi, mariuz, I want to switch my web based app from MySQL to Firebird and I'd like to know if It's safe to use rc6.
I'm not going to bring it in prod soon and I'd love to evaluate a more recent version than 1.0.3, but I don't want to get stopped to soon by the db ... my own errors are enough ;-)
BTW:
goreXP what's your problem with Firebird? Do you absolutely need a new feature and the team is too slow in rolling it out?
Posts: 303
Time spent in forums: 1 Day 6 h 45 m 28 sec
Reputation Power: 21
Quote:
Originally posted by pabloj Hi, mariuz, I want to switch my web based app from MySQL to Firebird and I'd like to know if It's safe to use rc6.
I'm not going to bring it in prod soon and I'd love to evaluate a more recent version than 1.0.3, but I don't want to get stopped to soon by the db ... my own errors are enough ;-)
BTW:
goreXP what's your problem with Firebird? Do you absolutely need a new feature and the team is too slow in rolling it out?
firebird 1.5 is scaling better than 1.0.3 and rc6 is
like a pre release version . I think only small bugs
will be found until the final . So is a better ideea to develop on it , when you finish the project the final
realese will be out .
Now is time for a good story with fb 1.5 from our lists
Quote:
just wanted to pass this along for your encouragement:
Due to following the suggestions in the FB support and development
newsgroups over the past month we were able to greatly improve the intense
processing of our master databases. To recap, the changes made were:
Upgrade from Windows FB 1.02 SS to FB 1.5 RC5 Classic (to use multiple
processors)
Fix all indexes that had a huge amount of duplicates
Take the duplicate record check out of import and make it it's own
process
Change the duplicate record check logic
These suggestions were made by Nickolay Samofatov, Sean Leyne, Alexander
Nevsky, and others.
The result: The normal 23 hour processing of our largest database was
reduced to 2 hours! And the server has now been running multiple databases
with no "lockups" for over a week now. Database backups and cleanups run
smooth and the sweep (after deleting 3 million records out of around 7 to 9
million) takes only 3 to 4 minutes rather than hours or even days.