0
Welcome Guest! Login
0 items Join Now

SOLVED 3.x Rocket Launcher and WAMP

Last Post
Search Topic

  • SOLVED 3.x Rocket Launcher and WAMP

    Posted 11 years 6 months ago
    • I was having some problems installing the 3x RocketLauncher for Acacia on my Windows machine using WAMP. It would hang on creating database tables.

      After an hour or so of searching I came across this: http://www.truexense.com/2013/08/how-to-install-joomla-31-on-wamp-server.html

      Once I downloaded WAMP v. 2.2e it worked.

      Just sharing in case anyone encounters a similar problem.

      Tag: Rocket Launcher Stuck Creating Tables
    #1024163
    • Who?'s Avatar
    • Who?
    • Preeminent Rocketeer
    • Posts: 25562
    • Thanks: 613
    • Joomla freelancer

    Re: SOLVED 3.x Rocket Launcher and WAMP

    Posted 11 years 6 months ago
    • Joomla 3.1 installation in general will stop on the database and tables creation screen if php execution time in php configuration is set too low. Sometimes, if you have execution time set to, for example, 30 seconds and you have slow DB server, tables creation will break and will run indefinitely. If you increase max_execution parameter in php config, installation will proceed normally

    • The following users have thanked you: Edson_LG

    • Check my services at: Mihha-Vision
    #1024420

  • Re: SOLVED 3.x Rocket Launcher and WAMP

    Posted 11 years 6 months ago
    • All good points. From what I gathered in that post switching the .sql to use MyIsam engine instead of InnoDB Engine does the trick.

      I did that first for Joomla's SQL file but quickly realized that RocketLauncher has a few more .sql files for content that need to be imported and rather than change the engine on all of them I just downgraded WAMP.

      I haven't looked into Joomla's forums yet to see why they're sticking w/ InnoDB, MyIsam works just fine but I figure it's a bit too technical for me to remain interested beyond 'what works'.
    #1024531
    • Who?'s Avatar
    • Who?
    • Preeminent Rocketeer
    • Posts: 25562
    • Thanks: 613
    • Joomla freelancer

    Re: SOLVED 3.x Rocket Launcher and WAMP

    Posted 11 years 6 months ago
    • Switching to MyISAM instead of InnoDB wouldn't be good in case you plan to use RokGallery for example because RokGallery wouldn't work at all

      The main differences between InnoDB and MyISAM are support for "referential integrity" and "transactions".

      If you need the database to enforce foreign key constraints, or you need the database to support transactions (i.e. changes made by two or more DML operations handled as single unit of work, with all of the changes either applied, or all the changes reverted) then you would choose the InnoDB engine, since these features are absent from the MyISAM engine.

      Those are the two biggest differences. Another big difference is concurrency. With MyISAM, a DML statement will obtain an exclusive lock on the table, and while that lock is held, no other session can perform a SELECT or a DML operation on the table.

      Those two specific engines you asked about (InnoDB and MyISAM) have different design goals. MySQL also has other storage engines, with their own design goals.

      en.wikipedia.org/wiki/Comparison_of_MySQL_database_engines
    • Check my services at: Mihha-Vision
    #1024572

  • Re: SOLVED 3.x Rocket Launcher and WAMP

    Posted 11 years 6 months ago
    • Excellent information and I'm glad you took the time to post it. Now that I know I'll stick close to InnoDB and avoid any 'workarounds' that suggest otherwise.

      Thank you!
    #1024770

Time to create page: 0.036 seconds