In this post, I’d like to do two things. First off, I want to plug a really cool site called PortableApps.com that has some really cool software in the form of … well, portable apps. What these are, are common widely used applications that have been transformed in such a way that they can run right off of your thumb drive, no install necessary, hence the term portable. They have lots of cool stuff that you can download, absolutely free, and use right off your thumb drive, or hard drive, or anywhere really. It’s nice being able to have firefox and open office (and much more) with you, no matter where you go, even with all of your own settings and customizations. That’s hard to beat! Go check it out, you won’t be disappointed I am sure. Read the rest of this entry »
Archive for the ‘MySQL’ Category
27
Great stuff at PortableApps
24
MySQL and the dreaded Error: 1251
Recently I ran into a situation when upgrading from MySQL 4.x to 5.x on a dev box of mine. I actually ran into this a year or two ago too, but I forgot to document it (I know, I know) and so I didn’t remember it. I thought I would post it here now to share with all of you in case you run across it yourself. Once the upgrade was done, the application that connected to the database would connect no longer. I kept getting authentication errors no matter what I did. This was a fresh install, I just imported MySQL dump files for my databases, so I thought it was a setting or something that I had forgotten. I checked everything out and could find nothing wrong with the settings, user accounts, passwords, you name it. The app I was launching ran on Windows (specifically, this is my EQEmu server, check it out daBoneyard), and it’s a console app so the Dos window flies by and I hadn’t seen the error message. Finally I decided to put a pause in the batch file and see what the heck was going on. It was then that I was presented with the following error:
26
MySQL Error Handler For PHP
Anyone that works with MySQL and PHP knows that it’s a good idea to trap and handle errors as a part of making calls to the database. I have seen folk that do it in many different ways, and some that don’t do it at all. It’s a real handy thing to do, especially in the early phases of development. If there is a problem somewhere in your code, good feedback from the application can make troubleshooting much easier. I tend to write functions that make life easier, put them all into a file and then reference that from my pages that actually do the work. In this case, I have a function that will catch and return MySQL errors, along with the query so you can see what is going wrong. First I will show you the function, and then I will show you some usage examples.
3
mysqldump tricks
In a recent post we talked about using the ever more awesome mysqldump command to dump the schema or structure of a table, but not the data. For example, if you want to create a copy of the database with new data.
I thought I might expand on mysqldump and talk about some other useful things you can do with your data. Let’s start by putting this into perspective. Since we are talking about the mysqldump command, obviously whatever we are doing is going to focus on getting data out of the database. Hence the “dump” portion of the command. This can be to backup the database, to clone it or move it, or in development/test/verification situations where you are taking part of the data and doing something with it.
22
Dumping MySQL database schema but not the data!
How many times have all you command line warriors out there been working with MySQL and backed up or moved a database with the trusty old mysqldump command? I know I use it all the time. But! What if you want to dump just the schema or structure of the database, and not all the data? Like going from DEV to TEST or PROD for example? You want to get the database setup, but you certainly don’t want all that data.
19
Sun Microsystems Buys MySQL
Wow. That’s about all I can say initially. I am sure I don’t have to explain anything about Sun or MySQL to most of my visitors, and anyone that knows me already knows that I am a hardcore user and supporter of both. I don’t know though, if this announcement is good news or not. I think only time will tell on that one. Really, it all will come down to what Sun decides to do with MySQL. They have an opportunity to help MySQL grow and become even bigger … but then again, they can drop the ball and make it flounder as well. I seem to remember a note a while back about Sun buying PostgreSQL too, I’ll have to look back and see if that ever came about, and if so, what ended up happening with it. For now we’ll all wait and see! Read more here …
