vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB3 Programming Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=15)
-   -   Question about mySQL version (https://vborg.vbsupport.ru/showthread.php?t=111002)

RMS-Chef 03-21-2006 05:15 PM

Question about mySQL version
 
Hi folks.

I am currently running MySQL v4.0.25-standard on my box. I have a new script that requires at least v4.1.x but I am unsure about compatibility.

Just looking for some general advice on this. We run a dual Xeon 2.8GHz with 4GB RAM and FC3 with CPanel.
  • Generally speaking, would going from v4.0.25 --> v4.1.x break anything? I know you can't say for sure but I don't think this is a huge version jump....or is it?
  • If the above is a relatively safe upgrade, what specific version would you suggest for best compatibility, speed and reliability?

My server management people claim that they always make a backup before the version upgrade so that I can revert if there are any major problems. We host a couple vBulletin sites and some customers have some pretty standard scripts running such as Nuke, PhotoPost, phpBB, etc.

Any advice before I give the server management people the thumbs up would be helpful.

Thanks.

Xenon 03-21-2006 09:35 PM

a plain vb will run perfectly on 4.1, it runs as well on 5.0

so standart scripts should run all, at least if the version is mostly up to date. some very old versions MAY have problem but as those versions are a security risk as well, people should upgrade ;)

of course you cannot say for sure because of custom scripts

Paul M 03-21-2006 09:43 PM

Quote:

Originally Posted by RMS-Chef
  • Generally speaking, would going from v4.0.25 --> v4.1.x break anything? I know you can't say for sure but I don't think this is a huge version jump....or is it?
  • If the above is a relatively safe upgrade, what specific version would you suggest for best compatibility, speed and reliability?

Generally speaking, no, it won't break anything. While we were still running on cpanel I moved our test and live from 4.0 to 4.1 without any issues.

We now have new servers that use Plesk rather than Cpanel, and we used yum to upgrade them to 4.1.15 without any issues.

RMS-Chef 03-21-2006 11:09 PM

So any advice on which version or does it really matter?

Is v4.1.15 ok as Paul has mentioned or any suggestions on a different version?

Xenon 03-22-2006 11:39 AM

well of course it's ok as Paul said, but recommended by MySQL is 5.0.19 so i'd use the newest recommended version, and maybe give people the possibility to optimize their scripts


All times are GMT. The time now is 05:55 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01096 seconds
  • Memory Usage 1,719KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (5)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete