Archive for the ‘Database’ category

New PDF database magazine

November 19th, 2009

No, it’s not from me or WebDevPub, but it looks good all the same.  It’s actually a continuation of the earlier MySQL Magazine, but with a larger focus, and is now a pay-for PDF, similar to JSMag and GroovyMag.

OSDBZine.net is put out bi-monthly from Keith Murphey, who had started the MySQL Magazine two years ago (and recently interviewed on webdevradio).  I just picked up the first issue, with a whopping 61 pages of database goodness.  With pieces on Drizzle, Firebird, PostgreSQL, MongoDB, LucidDB and more, it’s got something for just about everyone.

Only drawback so far is the current signup process – it’s a little barebones (I spoke with Keith, and he’ll be updating it soon).  Visit http://www.osdbzine.net/signup.html to register an account, then login to purchase via paypal.

Oracle buying Sun – what does this mean for MySQL?

April 20th, 2009

Just woke up this morning to news that Oracle is buying Sun.  After cursing myself for not having bought some JAVA last week when it was in the 6 range (pre-market now at 9.10), I started thinking about what this might mean for MySQL.

About a year ago, Sun purchased MySQL.  Although a lot of hooha was made about what might happen to MySQL at that time, Sun made it pretty clear that they wouldn’t be changing too much of the company they were purchasing.  They’d wanted to have a good story on the low-end of computing (from what I remember) and the LAMP stack (where M was for MySQL) dominated much of the low-end of web development.  While it was never on the same level as Ebay buying Skype, I think a lot of people were confused by how Sun would be able to get back the billion dollars they expended on the MySQL deal.

Fast forward a year.  Some of the key MySQL core team have left, forking the MySQL product in the process (drizzle).  Is the MySQL branch of Sun very attractive?  I imagine Oracle was looking more at the hardware and consulting side of the Sun acquisition, not the database side, but this won’t site well with many in the MySQL world.

The MySQL community has always been a bit suspicious of Oracle.  Many were quite alarmed when Oracle purchased InnoDB, the company that made the innodb MySQL table engine, and that was something that spurred on work on other transaction engines in the MySQL world.  Nothing has yet come to be adopted as widely as innodb yet, and Oracle’s control of InnoDB has continued to be a bit of concern for some in the community. 

Is Oracle getting much on the database front when they purchase Sun?  There’s probably not enough of a marketshare between the two to claim that there’s some sort of monopoly anti-trust considerations to take in to account (MSSQL, DB2 and PostgreSQL – what is their combined marketshare?) 

Is there a danger that “MySQL” as a product will be a name brand, but that many people will just start using community forks?  I can see that “MySQL” as a database engine might end up being a generic term, somewhat like “Linux”, in that there are many distros out there serving different needs.  Not sure if the MySQL licensing would ever allow for that degree of diversity, but maybe we’ll see something like this in reaction to the Oracle purchase. 

Side question – what will this do to Java and OpenOffice?  Hopefully Oracle will leave these (and MySQL) intact, and just focus on integrating these technologies in to their sales and consulting process, but leave the tech direction alone.

Responsibility, liability and cloud computing

July 27th, 2008

I was browsing High Scalability this morning and came across this article which got me to thinking about something I’ve not seen discussed yet when talking about ‘cloud computing’ in all its forms: liability.  I’m not talking about downtime, though that’s an issue in and of itself.  Looking specifically at S3, Google’s bigtable, and other similar services, what are the legal ramifications which you face if someone steals your customer data which you store in one of these hosted services?

I’ve not signed up for these hosted services yet so I’ve not reviewed the specific Terms of Service.  I’d have a hard time believing they’ll take *any* legal responsibility for lost or compromised data, even if it’d demonstrated that there was a security breach (physical or otherwise) in their infrastructure.  Why would they?  Perhaps some case law will eventually be established, but I’d be fairly nervous about putting large amount of customer data in to anyone’s inrfastructure that I couldn’t audit/control.

This is a tough call, really, because it’s fairly obvious that Google, Amazon, etc. have pretty smart people working for them, and likely are better at security than my organization might be.  That may be true, but it still doesn’t mean I can take a look at how they’re handling things, and doesn’t really give me much of an excuse if my customers’ data gets compromised.  If anything, S3 and others will likely be a bigger target for more advanced criminals to target.  Yes, it’s likely more secured, but the payoff will be much bigger.

Is this an acceptable risk for you, putting customer data in the hands of others for whatever reason?  To some extent we all do it – I’m putting customer data on servers in data centers where I don’t always have direct physical access.  I can lock down the machines via software as much as possible, but it’s not a perfect option, certainly.  Going the next step and just moving your data in to databases over which you basically only have read/write functionality seems like too big a step for me at this point, at least for sensitive data.

Are you using these ‘cloud’ services yet?  If so, what’s your take?

WebDevRadio podcast series – Interview with Brian Moon on scaling LAMP

May 3rd, 2008

This is the last in my MySQL conference series.  Brian Moon, author of Phorum and Sr Developer at Dealnews.com, sat down and gave a recap of his two presentations.  We have here nearly a full hour of his insights in to PHP/MySQL scalability, both with an app like Phorum and a more complex environment like Dealnews.  The sound was pretty good, although there was a hum in the background I tried to get rid of via ‘noise removal’.  I think this still sounds decent.  Let me know if the sound is too awkward and I’ll give it another pass if need be.

Thanks to Brian for going over things in such detail!  I hardly asked any questions, as I was trying to soak up as much as possible for myself, and I picked up more than a few useful nuggets.  He also touched on the future of the PHP//MySQL combination with the MyQSLnd (“next driver”?  I forget now!) driver being developed.  There’s some great info in here – listen up!

Also, as a reminder, if you have any job postings for your company, please help build up the WebDevRadio Jobs board at http://jobs.webdevradio.com, and thanks to the first few posters who’ve helped get things rolling.  :)

New jobs board at jobs.webdevradio.com

April 29th, 2008

I’ve been meaning to do this some time, and finally found the time to do it – jobs.webdevradio.com is up and functional (though quite empty at this point!) One of the things I mentioned on my podcast (webdevradio.com) one more than one occasion is that I tend to attract recruiters. Rather than just politely decline, I thought offering a web board focused on web development jobs would be more useful. Yes, there are many other boards that have come up in the past couple of years, but I might be able to do something different.

Pricing

I plan on keeping the postings and main system free for use, though I reserve the right to remove spam/mass posting.

Future plans

I have a somewhat unique opportunity to also promote jobs via the podcast. I’d planned a webdevjob podcast some time ago, but have too many projects on my plate as it is. If this new jobs.webdevradio.com web development job board becomes useful for enough people, I will revisit the jobs podcast idea again.

Category specificity

I’ve got categories for PHP, .NET, Java, etc.  I’m wondering if this is the best way to go, considering that many positions do require multiple tech.  Is this too narrow of a focus?  Or do you still think of jobs as primarily a Java job, even if some Python may be involved, for example?

Please post any open positions

If your company has any openings, please consider posting (or reposting) them at jobs.webdevradio.com.  I’m looking to have a few base jobs in many of the categories before I announce it on the webdevradio.com podcast.  As I said before, this may turn in to more of a hybrid job service, with a podcast series to go with it as well.

Thanks!

Why I think PDO sucks

April 2nd, 2008

Every so often I try to use PDO under PHP5, and every time I run in to basic functionality problems with no ability to find out what’s going on under the hood.  A recent example:

$dbh = new PDO(‘mysql:host=localhost;dbname=db’, “user”,”pass”);

$stmt = $dbh->prepare(“SELECT * FROM table where service_type = ? and name = ? “);

if ($stmt->execute(array(2,$short_name))) {

….

The ‘if’ line is giving me a FATAL_ERROR “accessing execute() method on a non-object”.

So the ‘prepare’ statement didn’t work.  But why not?  Throwing a try/catch around the prepare statement caught nothing – it just happily went on to try to execute the sql against $stmt even though it wasn’t an object.  How do you debug this stuff?  There’s no docs I can find on debugging this sort of behaviour, and given that PDO is a few years old, I shouldn’t have to.  BTW, I know it’s out of date – this is 5.1.6, so I am going to try to update today.

Another thing – how do you see what the final SQL statement sent to the DB would be?  Again – never seen any docs on this.  Go ahead – embarrass me and show me where this is documented so I look like a complete jerk.

If PDO was as good as it should be, I don’t think there’d be such a movement underway to rewrite a PDO2, which appears to be the case.

Also, in the docs, there’s *mention* of “if prepare doesn’t work you’ll get back FALSE”, but *no* examples show ‘proper’ behaviour of checking if your $stmt is an object or FALSE.  Some examples do show try/catch, IIRC, but that doesn’t seem to work (again, at least in 5.1.6).

Prove me wrong, someone, please.

SQL Server driver for PHP5

February 9th, 2008

For anyone that has struggled with using PHP and MSSQL over the years, this one may come as some pleasant news (if you’re still in that situation).  Microsoft has put out a preview of “SQL Server 2005 Driver for PHP” back in October 2007 (yeah, I just found out this morning!).  Ehh… not as impressed as I thought I would be, in that it’s still only for PHP apps deployed on Windows.  This isn’t replacing freetds any time soon.  I guess I’m still wondering what the market for “PHP apps deployed on Windows talking to SQL Server” really is – most of the shared hosting accounts I’ve seen, even on Windows, offer MySQL or Access as the database. 

Scratch that – I’ve started to see SQL server as an option more recently (bit of a brain pause there a moment ago!).  This is perhaps a bit of a chicken/egg situation – if there’s a more stable driver, this may help hosting companies push SQL Server as their default DB option (perhaps eventually charging for a MySQL installation as an option?).

There’s a video of the team talking about the project here (but you’ll need silverlight to watch it!) and the team’s blog here.

Powered by ScribeFire.

Sun buys MySQL and other interesting tidbits

January 16th, 2008

Sun is acquiring MySQL


OK, well, I thought I’d be able to find a few more interesting tidbits, but these two are interesting enough to me for a Wednesday morning.  Obviously the Sun/MySQL thing is big – will they use the acronym SPAM for Solaris/PHP/Apache/MySQL?  I claim “first post” on inventing that acronym, although I’m sure I’m not the first.  Or perhaps Java Apache MySQL (“JAM”)?  Or maybe even MySQL Apache Sun (or Scripting) Java (“MASJ”)?  Pronounce MASJ as “message” spoken in the Deep South.

But seriously, given my current work with Open Source Risk Management (OSRM), I’m really curious as to what this will do for MySQL licensing.  Sun has a history of really bizarre licensing (‘Sun Community Source License’, anyone?), and making their licensing byzantine enough to require people to be more paranoid about Sun stuff than other projects.  I truly hope most of those issues are vestiges of a “pre Schwartz” time, and that going forward Sun will be much more direct and simple about their licensing terms.

Additionally, what might this do for MySQL/Java integration?  I don’t think there’s been much of anything there so far, but maybe we’ll see the ability to do in-db scripting in Java?  Integrate Lucene as another available storage engine?  At the very least, perhaps they’ll start bundling JDBC drivers directly with MySQL so you don’t need to go download them separately (though, IIRC, it’s IBM that owns JDBC stuff, not Sun).

phpBB is running on the Project Zero PHP interpreter (written in Java)
The ProjectZero team is moving along on their PHP interpreter.  I’ve been watching it here and there since middle of last year (well, perhaps September?)  I’m mixed on this, but in general I think it’s a good idea.  It may serve as a catalyst for some people to start straddling the PHP and Java worlds more directly, and may lead more people to Groovy as well.

Anyway, any thoughts from any of you out there on these two recent annonuncements?

MySQL oddities in legacy project

December 22nd, 2007

I recently inherited a project.  My primary goal is to make it portable to the extent that it can run on another webserver setup.  This is a PHP4/LAMP system, but the people I’m getting it from didn’t write it themselves, and can’t spend the time to dig in to it and make it able to run on other systems.  Sort of a long story, but the crux of it is is that I’m having to do some cleanup.  I’m going to make this run under PHP5.2, but I’m looking at some things in the database dump, and they scare me.

One table has three columns which slightly freaked me out.  One column’s name is “DROP DATE”.  I KNOW you can get around using ‘reserved’ words by escaping the  column names, but the fact that this was written by someone who named a column ‘drop date’, using a space *and* two reserved words in a column name doesn’t inspire me with much confidence.  Another column’s name is “fall/spring/winter” – the slashes freak me out there, and the last one is “# users”.  Again with the space, and a pound sign as the first character – I don’t think I’ve seen so many weirdly named columns in one project.  I’m not even through reviewing the entire db schema yet, but these are enough to make me really cautious about the rest of the project already, and I’m barely in to it.

A table named ‘delete’ – just found that one too.  Sheesh…

Codemash free admission drawing giveaway

December 6th, 2007

The codemash organizers have graciously donated a free pass to the upcoming Codemash conference to be given away to one lucky webdevradio.com listener.  To enter in to the drawing, listen to the codemash episode interview podcast on webdevradio with Jim Holmes, follow the instructions, and hope your name is drawn.