#1
  1. Bug Hunter
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2003
    Location
    Transylvania (Romania)
    Posts
    309
    Rep Power
    24
  2. #2
  3. Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jun 2003
    Location
    Bucharest
    Posts
    72
    Rep Power
    12

    Exclamation yes ...


    ... and it show that it will not be the last RC
    Last edited by goreXP; September 11th, 2003 at 12:38 PM.
  4. #3
  5. Bug Hunter
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2003
    Location
    Transylvania (Romania)
    Posts
    309
    Rep Power
    24
    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
  6. #4
  7. Modding: Oracle MsSQL Firebird
    Devshed Supreme Being (6500+ posts)

    Join Date
    Jun 2001
    Location
    Outside US
    Posts
    8,527
    Rep Power
    539
    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?
  8. #5
  9. Bug Hunter
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2003
    Location
    Transylvania (Romania)
    Posts
    309
    Rep Power
    24
    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



    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.

    Fantastic!

    Thank you all very much!



    Don Gollahon
    gollahon@geneseo.net
    "The Original GenSoft Prodigal"
    My home page: http://www.firebirdsql.org and work place :http://www.reea.net

IMN logo majestic logo threadwatch logo seochat tools logo