• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "I blinking hate MySQL"

Collapse

  • d000hg
    replied
    Originally posted by NickFitz View Post
    I've used Navicat on good-sized databases (hundreds of thousands of records) and it worked well. However I find the current incarnation of Workbench is OK - it's basically Query Browser and Administrator munged together in one app, and the front page for managing connections is a bit cruddy, but the DB management stuff is fine and the Query Browser-equivalent bits are superior to Query Browser IMHO.

    All this is about the Mac versions, so other platforms may vary.
    It seems a decent basic SQL tool with a few bits glued on like editing a table in a form. I miss stuff like autocomplete though... is it 'game_id' or 'id', etc.

    I don't like the export though, it seems to insist on exporting everything with fully qualified names (db_name.table_name) and procedures with DEFINERs for the creating user. Makes for a few headaches (maybe there are options I didn't see).

    Leave a comment:


  • administrator
    replied
    I use SQLYog:
    MySQL GUI Tools. MySQL Monitor and Manager

    Can't live without it now, more than worth the cost IMO.

    Leave a comment:


  • NickFitz
    replied
    Originally posted by blacjac View Post
    I've used Navicat for MySQL a couple of times and found it quite good.

    Never used it in anger though....
    I've used Navicat on good-sized databases (hundreds of thousands of records) and it worked well. However I find the current incarnation of Workbench is OK - it's basically Query Browser and Administrator munged together in one app, and the front page for managing connections is a bit cruddy, but the DB management stuff is fine and the Query Browser-equivalent bits are superior to Query Browser IMHO.

    All this is about the Mac versions, so other platforms may vary.

    Leave a comment:


  • blacjac
    replied
    I've used Navicat for MySQL a couple of times and found it quite good.

    Never used it in anger though....

    Leave a comment:


  • d000hg
    replied
    Originally posted by minestrone View Post
    mySQL workbench is a pile of cack if you ask me, query browser and adminstrator are great tools and as good as any DB tools I use on 'serious' databases.
    I got workbench assuming as the 'official' tool it would be decent - it's OK but not a patch on the tools I'm used to like SQLDeveloper. I used to use TOAD with Oracle, I see there is a MySQL version - anyone tried it?

    And I know MySQL is a powerful, capable RDBMS for real-world use - it's just making me grumpy!

    Leave a comment:


  • Sysman
    replied
    Originally posted by minestrone View Post
    Now, I have theory that Oracle bought SUN to get mySQL to hinder its development, when mySQL went good with stored procs Oracle were not slow in buying the DB up. Don't think Oracle ever wanted Java, they wanted mySQL.
    Having seen how Oracle bought another database back in the nineties and then whacked the prices up I too think they wanted it more than Java.

    Leave a comment:


  • minestrone
    replied
    mySQL is a real world DB and can confirm that it can shift its arse when asked to do stored procs on large batch tasks.

    Now, I have theory that Oracle bought SUN to get mySQL to hinder its development, when mySQL went good with stored procs Oracle were not slow in buying the DB up. Don't think Oracle ever wanted Java, they wanted mySQL.

    mySQL workbench is a pile of cack if you ask me, query browser and adminstrator are great tools and as good as any DB tools I use on 'serious' databases.

    Leave a comment:


  • d000hg
    replied
    Originally posted by NickFitz View Post
    worked for me

    (To be precise, I did it in MySQL Workbench, and that's the SQL it generated to do my bidding.)
    I meant in a real-world DB where you have foreign keys and actual data in the tables

    TBF other RDBMs might be as bad but I don't recall Oracle being such a pig. I'm deducing that MySQL implements dropping the primary key by dropping and recreating the table based on the problems. Can't be arsed with all this dropping/re-creating FKs... let me write the stored procs and someone else can do the DDL!

    Leave a comment:


  • NickFitz
    replied
    Originally posted by BrilloPad View Post
    Was that available in 2008?
    The blog post is from 2003, so I'd say that's a "Yes"

    Originally posted by BrilloPad View Post
    If it was, and you knew about it, you could have made yourself a pot.
    Also available in 2008 was this book on which he's a co-author, so they could have saved themselves a pot by buying it: High Performance MySQL: Optimization, Backups, Replication, and More: Amazon.co.uk: Baron Schwartz, Peter Zaitsev, Vadim Tkachenko, Jeremy D. Zawodny, Arjen Lentz, Derek J. Balling: Books

    Leave a comment:


  • BrilloPad
    replied
    Originally posted by NickFitz View Post
    That's a limitation of the MyISAM storage engine, not of MySQL per se. Also, it can be resolved: Overcoming MySQL's 4GB Limit (by Jeremy Zawodny)
    Was that available in 2008?

    If it was, and you knew about it, you could have made yourself a pot.

    Leave a comment:


  • hyperD
    replied
    Nick Fitz on CUK Tech is better than Google!

    Leave a comment:


  • NickFitz
    replied
    Originally posted by BrilloPad View Post
    I remember JPM credit department worked on spreadsheets. So when they outgrew that they went to mysql. Shame when they reached the 4gb limit and everything collapsed.

    Thats what happens when boys design a system and bobs code it.
    That's a limitation of the MyISAM storage engine, not of MySQL per se. Also, it can be resolved: Overcoming MySQL's 4GB Limit (by Jeremy Zawodny)

    Leave a comment:


  • NickFitz
    replied
    I set up a table:

    Code:
    CREATE  TABLE `test`.`test_for_d000hg` (
      `first` INT NOT NULL AUTO_INCREMENT ,
      `second` INT NOT NULL ,
      PRIMARY KEY (`first`) );
    and:

    Code:
    ALTER TABLE `test`.`test_for_d000hg` 
    CHANGE COLUMN `first` `first` INT(11) NOT NULL  , 
    CHANGE COLUMN `second` `second` INT(11) NOT NULL AUTO_INCREMENT  , 
    DROP PRIMARY KEY , 
    ADD PRIMARY KEY (`second`) ;
    worked for me

    (To be precise, I did it in MySQL Workbench, and that's the SQL it generated to do my bidding.)

    Leave a comment:


  • BrilloPad
    replied
    I remember JPM credit department worked on spreadsheets. So when they outgrew that they went to mysql. Shame when they reached the 4gb limit and everything collapsed.

    Thats what happens when boys design a system and bobs code it.

    Leave a comment:


  • d000hg
    started a topic I blinking hate MySQL

    I blinking hate MySQL

    It won't let me do something as simple as change the primary key on a table. Open source crud.

Working...
X