Slashdot Mirror


MySQL CEO Interview

someonewhois writes "MySQL's CEO, Marten Mickos, says 'Open source & MySQL will rise, legal foes will fall', in a bold prediction that legal issues will continue to be ignored as a threat towards open source, and that software patents will harm the industry (well, duh)."

119 comments

  1. A little too bold.... by AtariAmarok · · Score: 5, Funny

    He'd better watch it before Bill Gates makes him an offer he can't refuse, and he wakes up with a penguin head in his bed.

    --
    Don't blame Durga. I voted for Centauri.
    1. Re:A little too bold.... by Anonymous Coward · · Score: 0

      a dolphin head, dude!

    2. Re:A little too bold.... by dcrocha · · Score: 5, Funny

      Bill: Marten, you do not yet realize your importance. You have only begun to discover your power. Join me, and I will complete your training. With our combined strength, we can end this destructive conflict and bring order to the database world.
      Marten: I'll never join you.
      Bill: I am your father.
      Marten: No. That's not true. That's impossible.
      Bill: Search your feelings you know it to be true.
      Marten: Nooooo. Nooooo.
      Bill: Yes I am.
      Marten: Ok then.

    3. Re:A little too bold.... by rjamestaylor · · Score: 1
      At first I thought your title "A little too bold"
      was in reference to Hemos' dept. string, to wit:
      From the dept.
      --
      -- @rjamestaylor on Ello
    4. Re:A little too bold.... by Anonymous Coward · · Score: 0

      edited... you forgot a part: Marten: I'll never join you. Bill: I am your father. Marten: No. That's not true. That's impossible. Bill: Search your feelings you know it to be true. Marten: SELECT firstname, FROM genepool WHERE son LIKE 'Marten'; MySQL: -> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near "SELECT firstname, FROM genepool WHERE son LIKE 'Marten'" Marten: Nooooo. Nooooo. Bill: Yes I am. Marten: SELECT firstname FROM genepool WHERE son LIKE 'Marten'; MySQL: -> Bill Marten: Ok then.

    5. Re:A little too bold.... by Anonymous Coward · · Score: 0

      Probably autoconversion to a blank of some NULL that MySQL automatically created. Remember, this is a database that gladly accepts February 32 as a date.

    6. Re:A little too bold.... by Anonymous Coward · · Score: 0

      Say! Could you two do an exercise in configuring Windows ODBC drivers as a scene from Taxi Driver? Just a request. Thanks in advance.

  2. 2 relevant sententces out of 38 by kpharmer · · Score: 4, Informative

    Not much here:

    What do you think was the top story in the Linux and open source arena in 2004?

    Marten Mickos:None of the legal attacks on open source or Linux have been successful. None of that stuff has gone anywhere. That's the biggest story.

    On that subject, MySQL has come to the conclusion that software patents will ultimately be demonstrated to be harmful to the industry. So, we are sponsoring a campaign in the European Union today to educate politicians and decision makers on the negative impact of software patents.

    1. Re:2 relevant sententces out of 38 by Frymaster · · Score: 1
      None of the legal attacks on open source or Linux have been successful. None of that stuff has gone anywhere. That's the biggest story.

      well, if you consider that the biggest threat to oss this last year was sco, it's not very surprising that the success rate for legal attacks has been low.

      but sco, really, is a bit player run by lunatics. if ibm or sun or any of the actually big-and-sane players decide to do a 180 on their oss commitment... well, that's a whole differnet, and scarier, kettle of fish.

      mickos' statements sound, to me, akin to saying "heavy rain has failed to damage this tank, ergo it is battle ready."

  3. Software patents by stratjakt · · Score: 4, Insightful

    Will harm *him*, but they'll help, for instance, Oracle.

    Both are in "the industry". So to make blanket statements like harm "the industry" fall on deaf ears.

    If you want to bitch about patents in a meaningful way, at least show how they do harm, by preventing competition by giving one company an unfair advantage.

    Also, it's in my opinion that it's only the frivolous patents that harm the industry. It's not the patent system itself that's wrong, it's the abuses of it. "Security holes" that need patching.

    --
    I don't need no instructions to know how to rock!!!!
    1. Re:Software patents by kpharmer · · Score: 5, Insightful

      MySQL certainly has a lot to fear from software patents: it's a commercial company that could be easily sued.

      And it's just now implementing functionality that other vendors put into their products 10-20 years ago. Many of these vendors have patents that cover some of the better approaches.

      Any idea which dbms patents mysql is stepping on most blatently? Does oracle have multi-version-consistency patented?

    2. Re:Software patents by Orgazmus · · Score: 1

      The patent system is way to outdated for a couple of patches. This baby needs a good rewrite :)

      --
      The system had the verbosity of HTML combined with all the readability of compiled assembly viewed as bitmap images
    3. Re:Software patents by Daniel+Dvorkin · · Score: 5, Insightful

      I think you're missing the point: he's saying (and I agree) that software patents harm the industry as a whole. Anything that benefits a few monolithic closed-source software providers like Oracle over many open-source providers like MySQL, PostgreSQL, etc. -- and please no "my DB can beat up your DB" flames, okay? -- is bad for the industry in general, no matter how many MiGs they enable Larry Ellison to buy.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    4. Re:Software patents by stratjakt · · Score: 1

      No idea, my only point was, to John Q Businessguy, and I. P. Lawyer, as long as someone's making money off them, patents are nothing but a good thing for the economy.

      --
      I don't need no instructions to know how to rock!!!!
    5. Re:Software patents by FlimFlamboyant · · Score: 1
      There's a fine line that needs to be walked when it comes to software patents. Either extreme will stunt growth.

      On the one extreme, if software patents run rampant and out of control, more monopolies will form, and new technologies will be slow to come forth, because almost regardless of the direction you go, you'll be stepping on someone's toes.

      On the other extreme, if you eliminate them altogether, there will be so much competition that there will be little to no profit from spending the time and money on research to produce new technologies. Sure, there are a lot of 30-yr-old geeks out there living in their parents' homes who are more than happy to develop them just for the challenge/fame of it, but even they have to eat sometime.

      --
      But God demonstrates his love for us, in that while we were yet sinners, Christ died for us - (Romans 5:8)
    6. Re:Software patents by GoofyBoy · · Score: 1, Troll

      >he's saying (and I agree) that software patents harm the industry as a whole.

      Does he really care about the industry? He cares about it because he cares about his company first. If his company became the entire industry (was a monopoly) do you think that he would care about the other companies who used to make up of the industry? Do you think that he would avoid sales or profits (short or long term) so other companies in the industry can benefit?

      Why do you care about the industry? Because it provides you a job? No, a company does that. Because you like programming? You don't need commerical ventures to do this, its can be a hobby?

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    7. Re:Software patents by stratjakt · · Score: 2, Interesting

      I know what he's saying.

      That's not the way most people see it. If someone's making money off it, it's a good thing.

      They don't think about the harm to competition or chill effects or anything so abstract.

      What I'm saying, is you have to show, with actual numbers, who's losing money because of software patents, or how end-users are getting screwed.

      Eolas v MSFT would be a really good example of frivolous patents hurting the industry, arguably one of the best. Of course slashdotters cant see past their anti-MS zealotry so it won't get a lot of playtime.

      --
      I don't need no instructions to know how to rock!!!!
    8. Re:Software patents by Karl+Cocknozzle · · Score: 1
      Will harm *him*, but they'll help, for instance, Oracle.

      I would say any help to Oracle, Microsoft, et al, would be very short lived.

      The benefit would only last until the point that somebody else had a patent on something they wanted to release. Then, their options are 1) Pay, 2) Fight patent, or 3) Abandon their costly research and make a different product.

      I don't know about you, but that seems like a prerrt big harm... to me, anyway.
      --
      Who did what now?
    9. Re:Software patents by Anonymous Coward · · Score: 0

      If it is so good for the industry, why don't we see the big patent holders doing a scorched earth patent enforcement drive? Because they would be hurt as badly as everyone else.

      The only reason IBM and now Microsoft are patenting everything they can is for protection. Anyone who would sue IBM is in breach of one of their patents.

      Smaller firms such as MySQL are at a disadvantage only because they don't have the deep pockets to sustain an expensive stable of intellectual property lawyers. SCO has spent $30 million or so on their suit. How much has it cost IBM to defend?

      The only industry that benefits from the current patent system is Legal.

      Derek

    10. Re:Software patents by Per+Abrahamsen · · Score: 1

      I'm not sure Oracle is big enough to benefit from software patents. In the medium time, it will benefit only three groups:

      a) a small number of very big companies (IBM, Microsoft), who will have cross-license agreements with each other, thus basically making themselves imune to the damage they do the rest of the industry.

      b) a larger number of small companies, who have no products of their own (and thus is invulnerable themselves), but make a living of selling patent rights to others.

      c) "ip" lawyers.

      In the long term, the damage done to the economy and society will damage *everyone*, but in the long term we are all dead, so that is not going to concern the above groups (except maybe IBM, who seem strangely enlightened about such issues).

    11. Re:Software patents by FuzzyBad-Mofo · · Score: 1

      Let's not mince words, anything that has the potential for creating lawsuits will have the backing of lawyers. And businesses like nothing more than wrapping up a market. But that doesn't address the point that software patents stifle creativitity and competition, and are a bad idea in general.

      Our current system of copyright is more than adequate to protect software implementations. There is no need for "process patents" (which is what software patents are, generally) which do not describe an invention in detail but simply describe a general idea or concept (see Amazon's "one-click" patent, etc).

    12. Re:Software patents by Anonymous Coward · · Score: 0

      Actually, software patents in their current form are bad for the economy.

      Patents were meant to give an entity a monopoly over something (call it productX) for a limited time. This was a market advantage for doing all the R&D and having a step up in getting profits. In return, they had to provide the public information on productX. The public could then use the patent to make alternatives to productX (little R&D) and pay royalties to the patent holder. Thus a very competitive, healthy economy would be nurtured. Plus, there would be a lot of incentive to innovate for the goal of obtaining that monopoly.

      Now for software patents, it doesn't work out as well.
      -First, the patent office is behind on the curve and giving out too many invalid patents. There doesn't even need to be a working model!!! Me just posting here probably infringes on someone's patents.
      -Second, the patents don't require source code, meaning the public doesn't get ANY benefit from them if there isn't any. They would still need to research and develop their own code.
      -Third, the lifetime of most software is a lot shorter than the lifetime of the patent. Meaning the patent holder isn't getting a limited monopoly, but an absolute one... which was always considered horrible as far as the economy is concerned.

      On the plus side, most don't take patents seriously. They see them as necessary defense weapons. Like IBM isn't going to bust me for posting here and infringing on their patent(s). Also, if you sue for patent infringment, you risk having your patent nulled. So software patents are generally mostly show and little bite.

    13. Re:Software patents by Anonymous Coward · · Score: 0

      my DB can beat up your DB!

      Oh wait.. Never mind.

    14. Re:Software patents by Anonymous Coward · · Score: 0

      As a whole, Microsoft, IBM, Oracle, etc. make up the majority of the industry. However you want to measure it, this is a fact. Employees, revenue, profit, market share, resources that can be applied to standards adoption, whatever. I don't like this anymore than you, but it's a fact that software patents are helping these organizations. Thus, for the most part, patents help the software industry. NOW, if you said software patents harm software progress or innovation, I'd agree with you. But the software industry does NOT actually need innovation to be successful. Again, sad fact, but it's true. Why is this true? Because I really believe ee can solve all the world's problems without any further innovation of software. We simply need to identify the problems, allocate resources to them, and we can solve problems with last year's technology just fine, thank you.

    15. Re:Software patents by Alsee · · Score: 1

      Well when some bastard is manufacturing landmines and strewing them about, and lobbying for stronger landmines, and lobbying for other countries to let them strew landmines over there too, they generally don't get a lot of sympathy when they step on a landmine themselves. In fact a lot of people HOPE the bastard will keep stepping on landmines and ether get killed or at least wise up and quit lobbying in support of them.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  4. GULP! by sanityspeech · · Score: 0, Redundant

    Open source & MySQL will rise, legal foes will fall...

    I thought MySQL IS open source!

    *shudders*

    1. Re:GULP! by dfetter · · Score: 2, Insightful

      Actually, MySQL is a lot more like shareware. For a real open source RDBMS, use PostgreSQL.

      --
      What part of "A well regulated militia" do you not understand?
    2. Re:GULP! by cmbofh · · Score: 1

      What exactly is shareware about the GPL?

    3. Re:GULP! by Anonymous Coward · · Score: 0

      MySQL is not an RDBMS. MySQL is a set of extensions for popular scripting languages which allow manipulation of large, heterogeneous arrays using a subset of the same command language as an RDBMS. For some applications -- e.g. keeping track of your CD collection, balancing your bank account, keeping a mailing list for a small club dedicated to an obscure hobby, running a small online shop with only a few customers a week, setting up a blog and so forth -- this actually is quite enough, and the missing bits can be emulated through the scripting language anyway. The blistering speed gained from not having to deal with stored procedures, triggers and subqueries in the backend almost makes up for the extra time spent emulating these features in your scripting language of choice.

      Of course, newer versions of MySQL almost certainly will incorporate these features.

    4. Re:GULP! by dfetter · · Score: 1

      If MySQL were only licensed under the GPL, it wouldn't be shareware. However, MySQL AB goes to a lot of trouble to make unclear the exact circumstances when you can use the GPL product vs. when you have to buy a commercial license. This campaign of fear, uncertainty and doubt is what differentiates MySQL from a FLOSS app.

      --
      What part of "A well regulated militia" do you not understand?
    5. Re:GULP! by jadavis · · Score: 1

      Yes, MySQL is GPL through-and-through, including its client libraries.

      That means that if you want to even support MySQL in your product (e.g. "my product supports MySQL, Oracle, and PostgreSQL"), your product needs to be GPL or you need to buy an expensive commercial license.

      It's a long tradition that client libraries are LGPL or BSD or something (which is why the FSF created the LGPL). MySQL broke that tradition, and also threatened the variety in open-source software by disallowing a BSD (etc.) application to talk to MySQL, requiring that it be GPL or commercial.

      If I'm not mistaken, that's actually more restrictive than many commercial database licenses.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    6. Re:GULP! by cmbofh · · Score: 1

      You may think what you want about MySQL AB's licensing policy, but sorry, the term shareware is utter nonsense in this context.

    7. Re:GULP! by jadavis · · Score: 1

      Yes, that is a little worrisome that MySQL is creating confusion about the GPL in particular and open source software in general.

      However, I'm fairly sure that MySQL is GPL, and no matter what they say, you can do the same things with MySQL that you can with other GPL software.

      Except how they made the client libraries GPL instead of LGPL. That, in my opinion, really stands out against the open source community. You can't have a BSD licensed (or whatever else) app support MySQL, it has to be GPL or you have to buy a commercial MySQL license. It goes against not only the interoperation of closed and open software, it also goes against the variety of open source software.

      In fact, commercial companies can simply buy a license to avoid the problem, a free software application can't buy a license, so it's GPL or nothing if you want to support MySQL.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
  5. Legal Woes by Locdonan · · Score: 1, Insightful

    But if open source advocates and creators spend all of their time in litigation, doesn't Open source suffer as a result?

    Their creativeness is put on hold, and the money for litigation has to come from somewhere. They usually are not in it for the money, so where does it come from?

    Corps with their deep pockets have an advantage; they can sit in a court room all day long, every day for years, dragging out the process and basically smothering out the open source comeptition.

    On the plus side, I guess there will always be someone to pick up the fight!

    --
    If I wrote something witty, you would say I stole it from somewhere.
  6. YOU ARE INCORRECT, SIR by Anonymous Coward · · Score: 3, Funny

    Postgre and Firebird are toys.

    MySQL is like the playmobile activity center you put in an infants crib, so that one day when he sees a real database he won't be too scared of it.

    1. Re:YOU ARE INCORRECT, SIR by Anonymous Coward · · Score: 0

      I'd say that MS Access is more friendly to the toddler market.

      And is nearly as robust as MySQL!

    2. Re:YOU ARE INCORRECT, SIR by AtariAmarok · · Score: 1
      "I'd say that MS Access is more friendly to the toddler market."

      I bet you think it is fun to give mousetraps and matches to little children to play with.

      --
      Don't blame Durga. I voted for Centauri.
    3. Re:YOU ARE INCORRECT, SIR by DrSkwid · · Score: 1

      hehe good call

      at a company I recently started consulting for the admin runs mysql on winserver (shudder)

      it locks up and his solution is a reboot !!!!!!

      not mysql's fault but still, I like the story

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    4. Re:YOU ARE INCORRECT, SIR by Anonymous Coward · · Score: 0

      JET supports transactions and subqueries. (JET is the DBMS behind Access).

    5. Re:YOU ARE INCORRECT, SIR by Anonymous Coward · · Score: 1, Interesting

      Also supports views and has limited procedure support.

      Just don't try to get more than 20 people using it at the same time. MySQL wins in that area, and ONLY in that area.

      Oh, and there's the entire Microsoft/Open Source deal. I'm really surprised more people just don't go with PostgreSQL or any other open source RDBMS that actually has a featureset comparable to commercial RDBMSs. I don't care if your RDBMS has things like replication support, support for multiple databases, etc., because as a small applications developer, I'll probably never use them. But if it takes you 5 versions just to implement views, your product is a joke.

      And I really think that the OS community needs to realize this.

    6. Re:YOU ARE INCORRECT, SIR by Robber+Baron · · Score: 1

      Troll, troll, troll...

      I run MySQL on W2K Server and it doesn't lock up...ever. Power failures are the most common cause of re-boots.

      Of course achieving that requires that you know something about configuring Windows servers. For a change, maybe instead of just bashing Microsoft every time there's a problem, maybe some of you anti-MS trolls should learn how to...um...actually do your jobs?

      --

      You're using her as bait, Master!

    7. Re:YOU ARE INCORRECT, SIR by DrSkwid · · Score: 1


      hence the "not mysql's fault" part

      it is a true story, what more can I say

      I had hoped that my text reflected on the admin, not the equipment

      calm the fuck down

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    8. Re:YOU ARE INCORRECT, SIR by arkanes · · Score: 1

      20?!? Christ. Try like... 2. At least if one of them needs to do an update. JET/Access is a file-backed database, it's not designed for multi user access. It's fine for, say, application level data persistance. It's competition in OSS world would be SQLLite, which is a file-backed embedded database with a simple api. MySQL, while widely used for reasons I don't understand, isn't well suited for that kind of application because of it's client/server model.

    9. Re:YOU ARE INCORRECT, SIR by imroy · · Score: 2, Insightful

      Oh, there are many of us in the OS community that know how pathetic MySQL is. The sad fact is that we're a minority. And thus you have the vicious cycle of most people using MySQL because that's usually that's available at web hosting companies, and that most web hosting companies only support MySQL because that's all they see demand for. *sigh*

  7. Ignore legal issues? by nurb432 · · Score: 4, Insightful

    Thats fine, when you are on the 'right' side of the suit..

    Let him get hit with being the defendant on a few IP suits, and i bet he sings a different tune.. One of caution..

    --
    ---- Booth was a patriot ----
    1. Re:Ignore legal issues? by iabervon · · Score: 1

      Depends somewhat on whether those suits would have been avoided by caution. After getting hit with IP lawsuits that you couldn't have avoided, one is more likely to decide to ignore legal issues, particularly in the case of patents, where being cautious may triple your legal liability without reducing your risk substantially.

  8. Geographic Information Systems by SsShane · · Score: 4, Informative

    As a GIS geek that wants a solution that costs less than $10,000,000.23, I'm hoping that MySQL improves their spatial extensions. Right now I play with PostgreSQL w/PostGIS until MySQL can implement more robust projections (how geography is "laid flat" on a map for those who don't know). From what I gather, and I admit being new to open-source GIS solutions, PostgreSQL w/PostGIS extensions stomps all over MySQL at the moment, but I think it would be in their interest to improve as they have a nice business model and GIS is taking off.

    1. Re:Geographic Information Systems by kpharmer · · Score: 5, Interesting

      get in line...

      MySQL is still implementing functionality common twenty years ago. And many of their enhancements of the last few years have left major gaps (innodb/replication awkwardness, etc).

      Additionally, they still haven't addressed their problem with silent exceptions (quietly truncating strings that don't fit, quietly converting numbers that don't fit, allowing invalid dates, etc, etc).

      So, yeah, it would be nice for them to pick up some OORDBMS functionality that postgesql has like spatial awareness, ip functions, etc - but I hope that they clean the product up first instead.

    2. Re:Geographic Information Systems by SsShane · · Score: 1

      Nice reply, thanks. I have no idea why you are marked as Troll though; I found it informative. Mods?

    3. Re:Geographic Information Systems by GigsVT · · Score: 3, Funny

      Moderations are stored in a MySQL database, which detects and silently converts moderations that are positive to ones that are negative, when they are attached to a message critical of MySQL.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    4. Re:Geographic Information Systems by juniorkindergarten · · Score: 1

      You've piqued my interest! I'd like to know more about your project, what's the name of it, website, etc? Thanks jk

      --
      "Every security scheme that is based on secrets eventually fails." - Steve Jobs
    5. Re:Geographic Information Systems by ajs318 · · Score: 1
      Additionally, they still haven't addressed their problem with silent exceptions (quietly truncating strings that don't fit, quietly converting numbers that don't fit, allowing invalid dates, etc, etc).
      Have you tried doing bounds-checking in whatever scripting language your frontend application is written in, before passing it to MySQL? MySQL just assumes you're smart enough to deal with stuff like that your own way if you don't like the way it's going to. Fortunately you do get to see exactly how MySQL deals with exceptions, and you can even change it if you don't like it.
      --
      Je fume. Tu fumes. Nous fûmes!
    6. Re:Geographic Information Systems by snorklewacker · · Score: 2, Insightful

      > Have you tried doing bounds-checking in whatever scripting language your frontend application is written in, before passing it to MySQL?

      You know, that's the same argument that Mac zealots were using about memory protection before it landed in OSX. "Applications should be smart enough to not access memory that isn't theirs".

      The whole point of a database is to secure the data integrity, and not worry about some random application screwing it up. MySQL is nothing but a storage engine if it can't handle that.

      --
      I am no longer wasting my time with slashdot
    7. Re:Geographic Information Systems by ajs318 · · Score: 1
      The whole point of a database is to secure the data integrity, and not worry about some random application screwing it up. MySQL is nothing but a storage engine if it can't handle that.
      This is like the thing with the electronic engineer and the mechanical engineer arguing over the watch with no moving parts. If you want all the checks and balances done in the backend, don't use MySQL.
      --
      Je fume. Tu fumes. Nous fûmes!
    8. Re:Geographic Information Systems by kpharmer · · Score: 2, Insightful

      > Have you tried doing bounds-checking in whatever scripting language your frontend application is
      > written in, before passing it to MySQL?

      yes, we used to exclusively rely on the application to manage data quality back in the 70s and early 80s (when using hierarchical databases, flat files, and ISAM). Of course, then we discovered that the procedural application code did a *horrible* job of consistently performing these checks, for various reasons like:
      1. checks changed over time, but the application programmer failed to revalidate 100% of the historical data.
      2. multiple application interfaces implemented checks differently (j2ee client vs .net client vs etc, etc).

      So, as of about 1984, I've been using these capabilities pretty extensively. Not to say that I don't also perform simple constraint-checking in the app - there are some usability benefits there. But the database provides a redundant, declarative, and failure-proof assurance of many constraints.

      > MySQL just assumes you're smart enough to deal with stuff like that your own way if you don't
      > like the way it's going to.

      No, MySQL suffers from quick development focused on marketing rather than engineering. These errors look more like oversights than deliberate engineering, they are misleading & inconsistent. Further, mysql is the *only* product I know of that claims to be a RDBMS that has these issues. How is any of this a good thing?

      > Fortunately you do get to see exactly how MySQL deals with exceptions, and you can even change it
      > if you don't like it.

      Oh sure, you read about these documented bugs - but you still won't get an exception for a numeric or string overflow, or invalid date. So, if you want your app to run on five different databases - you've got to write extra code for mysql - around its bugs.

      This isn't good engineering, it's sloppiness. And MySQL shouldn't get a free pass just because they're open source. We'd expect more from oracle, sql server, or postgresql. MySQL will fix these problems - since they're now courting commercial application developers they have no choice. But it's disingenuous to pretend that these bugs are deliberate.

    9. Re:Geographic Information Systems by SunFan · · Score: 1


      How many people really need GIS support in MySQL? There's you, of course, and ...?

      Since, it appears someone already stepped up with something in PostgreSQL for GIS, is there something about PostgreSQL that is unsatisfactory that requires MySQL, instead? Or is GIS just a feature check-box that people can troll about?

      --
      -- Microsoft is the most expensive commodity operating system and office suite vendor in the marketplace.
    10. Re:Geographic Information Systems by r3m0t · · Score: 0

      MySQL does not do bounds checking for speed. It does not cough and die when given stuff beyond the storage capabilities of the field.

    11. Re:Geographic Information Systems by LWATCDR · · Score: 2, Insightful

      "Have you tried doing bounds-checking in whatever scripting language your frontend application is written in, before passing it to MySQL?"

      ummm. I guess that OS's shouldn't have to worry about bounds checking since applications should never do anything stupid????

      If an Application can crash an RDMBS or put corrupt data in to a table that is a flaw. Do other RDBMS do the same? If not then they handle exceptions better than MySQL. Trying to make this a plus is just dumb.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    12. Re:Geographic Information Systems by jadavis · · Score: 1

      Really? I wonder what the difference in speed actually is. After all, checking the length of a string against information that is already in memory (the type of the field you're inserting into) is negligible compared to a disk write, which has to be done no matter what.

      So, you're saying that MySQL has optimized away that string comparison, even though it's probably less than one percent of one percent of the total cost of an insertion?

      Not only that, but the checking must be done somewhere. I just don't buy the speed argument at all in this case. I think it's more backwards compatibility than anything else.

      It's all a moot point to me because none of it is enough of a reason for me to give up my data integrity. If there's a bug in one application I don't want it to affect all the other applications accessing the same database.

      I'm sure there is some reason that so many people use MySQL. Actually, I would hope there is a reason; I'm actually quite ignorant about MySQL except for a few of the things that bug me about it. But anyway, avoiding a strlen() in an insertion is not one of those reasons.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    13. Re:Geographic Information Systems by SsShane · · Score: 1

      I don't NEED it. But they put some sort of "spatial" extensions in there, almost like an afterthought so I was amazed when I realized how limited it was. It also pushed me towards PostgreSQL which I was not aware of (I told you I was new; I come from planet ESRI) and I love it. Variety is the spice of life though, ask any Windows user...oh wait.

    14. Re:Geographic Information Systems by jadavis · · Score: 1

      What if you have 5 applications accessing the same database? Or 50?

      Well, if one of those has a bug, and one will, it may insert some inconsistent data. Then, another application will rely on the data following certain rules to function, and create another problem. This could actually cascade into new data inconsistencies.

      Now, here's the tough part: find the bug and correct the data integrity problems.

      I have had maybe 5-10 applications accessing the same database. I was very happy when I got one of those errors from the database because I knew exactly where the problem lay, and I knew the DB was still consistent and did not need to be corrected.

      Now, I know what you're thinking. Let's have the applications check the data before they put it into the database, and then also check the data after it comes back from the database.

      Well, start thinking about that a little bit. First, that's a huge amount of code. When an application checks the data, it must look at the internal consistency of the database (do all orders have an associated customer record? etc.), which is inherently more expensive and awkward than having the database check it. Then, what do you do when you find an inconsistency? What app put the wrong data in there?

      Also, to do that right is a lot of code. A lot. Just start thinking about it and you will see a huge amount of redundant, bug-prone code that requires its own set of tests. You can't reuse the consistancy code if you use more than one programming language. Now, how do you know it's working?

      Starting to look like yet more code and more bugs...

      Now, come up with a set of tools so you can correct inconsistencies when you detect them. More code, more bugs.

      So, if you're working with more than one application on the same DB, I would strongly advise using a database with consistency checking. After all, at one point in time there was no such checking on the db side. Then everyone started using it. Perhaps these are the reasons why.

      Even one app still runs into many of these problems (like how to correct mangled data after a bug in your application makes it inconsistent).

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    15. Re:Geographic Information Systems by arkanes · · Score: 1

      Right. If you want an ACID compliant database, don't use MySQL. If you really want an unusually slow filesystem, then go ahead and use it.

  9. Wait, wait, you're joking... by rhaas · · Score: 5, Insightful

    Here we have the CEO of a company saying, basically, that his company is going to do well this year.

    And just for making that unremarkable statement, he makes the Slashdot homepage?

    News flash! It's the CEO's job to promote the company. They all do that. Even Darl.

    1. Re:Wait, wait, you're joking... by SlinkyToad · · Score: 1

      Too True...

      I watched "Pirates of Silicon Valley" this weekend, an old made for TV special about the 80s rise of Apple and Microsoft. As impressed as I have been with Apple since Jobs took the reigns back in 1996, I am still keenly aware that Apple is equally as guiltly of trying to make me solely dependent on them as Microsoft.

      Just because your company works develops and distributes under the GPL doesn't mean that you aren't going to be tempted by the vast riches that come from having a monopoly in your software (or hardware) niche. ~

  10. uh, Hemos.. by froggero1 · · Score: 4, Funny
    from the dept.

    what department would that be exaclly?

    --
    ~/.sig: No such file or directory
    1. Re:uh, Hemos.. by Anonymous Coward · · Score: 0

      That would be the i-can't-be-bothered-to-check-the-article-let-alone -think-up-yet-another-'funny-dept-any-more-dept.

    2. Re:uh, Hemos.. by Frank+T.+Lofaro+Jr. · · Score: 2, Funny

      from the dept.

      From the (department name got lost because of lack of MySQL database consistancy) department, of course. Maybe Slashdot should switch to PostgreSQL, it is open source too. And then parts of the article title header would be safe from corruption, but our ideals would stay safe too. :)

      Happy Martin Luther King Day everyone! Google, why no special logo for today?! :(

      --
      Just because it CAN be done, doesn't mean it should!
  11. Not so fast ... by OMG · · Score: 1

    Given what I saw on last years 21C3 MySQL 4 will fall flat on its face if someone starts to test the security of this version of the product.

    The sas thing is: I am not kidding. Don't use too long usernames on the SQL client-side which could be (by coincidence) the same location where your SAP-System is installed.

    1. Re:Not so fast ... by Anonymous Coward · · Score: 0

      I went and looked at the linked site, which is in German, and had a German friend look at the copy. It didn't seem to indicate any issues with MySQL 4.

      The issue you raise is important, so could you explain a little bit more about the potential security issues with MySQL version 4?

  12. Original article /. ed by killmister · · Score: 0, Redundant

    MySQL CEO: Open source & MySQL will rise, legal foes will fall By Jan Stafford 13 Jan 2005 | SearchEnterpriselInux.com 2004 was a portent of things to come for Linux in 2005, both because of what didn't happen (SCO Group's victory) and what did (the rise of open source software), according to Marten Mickos, CEO of Sweden-based MySQL AB. In this interview, he predicts how those events, which included the success of MySQL's database, will play out in 2005. What do you think was the top story in the Linux and open source arena in 2004? Marten Mickos:None of the legal attacks on open source or Linux have been successful. None of that stuff has gone anywhere. That's the biggest story. On that subject, MySQL has come to the conclusion that software patents will ultimately be demonstrated to be harmful to the industry. So, we are sponsoring a campaign in the European Union today to educate politicians and decision makers on the negative impact of software patents. What trends in 2004 will have important consequences in 2005? Mickos: Large software companies, like CA, began coming to open source more strongly than ever before. In 2004, the thought caught on that open source indeed is a smarter way of producing software. It is of higher quality at lower cost and that is sort of a no-brainer. The examples are there for all to see -- Apache, Sendmail, PHP, Linux, MySQL -- and they've reached maturity, all being at least 10 years old. Also, Linux [cemented its position] as the fastest growing operating system. There is growth in adoption of all of the versions. There are the conservative parts of the markets that are staying with the 2.4 kernel, but there are the new guys that are going with the 2.6. I think that the sign of a maturing product is when new versions aren't that shockingly different anymore. Why did MySQL make so much progress in the enterprise market in 2004? Mickos:We've been working with the enterprise market and getting ready for the enterprise market. So, in 2004, we wrapped up our services packages and built a consulting team. We came out with new versions, specifically 4.1. Now, we are getting ready for 5.0 next year. In terms of partners, we've established and are starting partnerships with strategic partners that are needed in the enterprise space. What will be the important trends in the Linux and open source space in 2005? Mickos: We will see increased growth, faster growth than before, in adoption of open source in the enterprise, not just for MySQL, but across the board. I think that JBoss will be experiencing a lot of growth. The new, slightly younger companies -- like SourceLabs and SpikeSource -- that are coming up will enjoy that growth. There are more enterprise customers who are ready to take the step because IBM, HP, CA and most of the other big companies are standing behind open source. What challenges do you see facing businesses that are going to start using more open source software in 2005? Read more on open source databases here MySQL exec: Open source to be New Year's resolution for many CA swings at Oracle, MySQL with Ingres Mickos: We deal a lot with enterprise customers, and we ask them what problems they foresee and what questions remain unanswered. Their No. 1 concern is training the staff. They are asking themselves whether they need to retrain people or whether they have the skills in-house already. The good news is that most corporations discover, when they ask around, that they have open source skills in-house. That is an important milestone for the open source movement. Many corporate IT people have used open source products at home or, sometimes secretly, in business projects. Of course, formal training may still be needed. That is the big hurdle that large organizations need to jump as they adopt more open source. What is ahead for MySQL in 2005? Mickos: We will come out with version 5.0, which is a very significant release for us. It will have many new features that customers have asked for, and will make MySQL even easier for large and small corporations to use.

    --
    MySQL Error 1040: Can't return sig, Too many connections!
  13. Don't you dare... by Faust7 · · Score: 1

    Don't get complacent, Mr. Mickos. Don't you dare get complacent. Complacency is the state people get into just before some legal challenge arises out of nowhere and kicks them in the head. The only proper mindset to have with respect to legal issues is paranoia. You have to strategize for every possibility and then some.

  14. Phew by Bluetick · · Score: 3, Funny

    And here I was expecting him to say "Hey, sell your shares, this company and this open source stuff is fucked." Well this is a relief.

    1. Re:Phew by Anonymous Coward · · Score: 0

      LOL inn'it! Mod parent up funny.

  15. let's see by N3wsByt3 · · Score: 1

    That is a rather limited view. Seen that research indicates that softwarepatents actually hinder innovation, one could as well say that it is, at the end, NOT a good things for the economy *as a whole*.

    When you have less innovation, ultimately your products and your businesses get behind, which will lead to a far bigger economical deficit then some IP lawyer could ever make the economy 'recuperate'.

    On an individual level and short-time period, level, you will have people benefitting and people losing out when sw patents are allowed (or not). On the long run and for the economy as a whole, you will lose out if you create or maintain software patents.

    --
    --- "To pee or not to pee, that is the question." ---
  16. caring about the 'industry' by N3wsByt3 · · Score: 2, Insightful

    "Does he really care about the industry?"

    Maybe he does, and maybe he doesn't, but that's not the actual point. Even if he would turn out to be a greedy bastard who wanted to monopolise the entire industry (as MS does), the question remains if sw patents are a good idea or not.

    Good isn't good for this or that corporation in the short term, but for society in the long term. After all, a patent is a monopoly given by the state, and the state is (supposed to do) what's good for their citizens. Ultimately, in a democracy, *we* define the state. So the question boils down to: is it a good thing for the populace as a whole?

    As we all know, monopolies are never a good thing, and the only reason why it is given, is because it is supposed to stimulate further innovation. at least on sw patents enough studies have been done to indicate they don't do that at all, on the contrary.

    Conclusion: it is NOT a good thing. (Even when a particular company might profit from it at a given time).

    --
    --- "To pee or not to pee, that is the question." ---
  17. Minor niggles about MySQL AB by tod_miller · · Score: 1

    Their dual license model is great, but I think they cloud a little the GPL licensing and commercial licensing:

    If you distribute MySQL Software within your organization, you should purchase a commercial license.

    GPL is not at all restrictive!! They mention this as being restrictive, basically they represent GPL as a less viable option for many companies than it really is.

    Anyway, kudos for being a corporattion willing to tag itself GPL (even if otherwise it would have meant marketshare death) :-)

    --
    #hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
    1. Re:Minor niggles about MySQL AB by ajs318 · · Score: 1

      Well, as long as your internal distribution is subject to the conditions for which the GPL grants permission to distribute software, then you are fine. The "grey area" is internal distribution of modified software in binary form only {or are you doing no such thing, just keeping the sources in salt for the rest of the department?} That could even be construed as fair dealing, permissible under copyright law; the GPL cannot block it and remain compatible with your statutory rights. At any rate it would only be detectable illegally.

      GPL makes sense for corporations, because it prevents anyone else from making a closed-source derivative. If you use a BSD-like licence, you have to be very careful; if some competitor tweaks your source to make an incompatible derivative, and launches it as closed-source with an expensive advertising campaign, you could well be squozen right out of the market unless you hit back quickly with something which is both free and compatible with their version.

      If you buy the commercial licence, you are buying a support package -- that's what the MySQL company has that customers want, and letting them have the software without paying for it isn't cutting their throat. Distributing it as source code means it can be run on damn nigh any hardware, which maximises the customer base. And letting users tweak it themselves means that the MySQL company get all the best tweaks to use in their next version -- but they can't deny those tweaks to non-paying users either! Best of all worlds, really.

      --
      Je fume. Tu fumes. Nous fûmes!
    2. Re:Minor niggles about MySQL AB by Anonymous Coward · · Score: 0
      Anyway, kudos for being a corporattion willing to tag itself GPL (even if otherwise it would have meant marketshare death) :-)

      Even if it's lies?

      If you wish to ship MySQL as part of a commercial distribution, they will try to make you pay the commercial license fee. MySQL is available under the GPL. Read the GPL and please tell me how they can justify this.

    3. Re:Minor niggles about MySQL AB by Anonymous Coward · · Score: 0
      ...you could well be squozen right out of the market...

      Heh. "Squozen". I've found my new ambiguous marketing word for the week. Now all I've got to do is convince sales and marketing that "squozen" is a well-known technical term, and that... hmm, let's see, that it's used to refer to a compressed, read-only file.

      "It's a combination of "squeezed" and "frozen", right? Used to refer to an immutable file, but it's not completely immutable, because it can be decompressed, and then it's unsqueezed, but still frozen... unsquozen. Microsoft introduced unsquozen file support with SP2 for XP, but most people aren't using it yet, because it's kind of hard for most developers to understand, what with the multi-threading issues. But we were in on the SP2 beta testing, so we've been working on unsquozen file support already, and it looks like we should be able to support 3rd-party squozen files in the next release."
      2 to 1 that I can get them telling customers how well we handle "squozen" files by the end of the week.
    4. Re:Minor niggles about MySQL AB by black+mariah · · Score: 0

      Because you fucking idiot, the commercial version is under a non-GPL license. Also, since you are obviously unaware of this, GPL != no cost. Please, actually read the fucking GPL before you start calling people out on it.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    5. Re:Minor niggles about MySQL AB by Anonymous Coward · · Score: 0
      Because you fucking idiot, the commercial version is under a non-GPL license. Also, since you are obviously unaware of this, GPL != no cost. Please, actually read the fucking GPL before you start calling people out on it.

      Get a grip of your life you complete and utter moron.

      If you obtain something under the GPL, you retain the right to redistribute it under the GPL.

      You are allowed to charge a reasonable fee for your time spend in copying it and for the medium upon which is is distributed.

      You are not allowed to charge a "license fee" top restrict other peoples' right to use, copy or modify the program.

      So if I obtain a copy of MySQL under the GPL, I should be allowed to redistribute it under the GPL.

      If I want to sell people some commercial software, or to give them some closed-source software, and provide them with MySQL as the accompanying database engine under the GPL, source and all (for MySQL) why the hell should I have to pay a single penny at all to MySQL?

      That was the point I was making. That is the tactic MySQL AB is employing at the moment.

      I believe that it is morally wrong, but more importantly, in violation of the terms of the GPL itself.

      Meanwhile, here as usual, all the weenies and fanboys have drunk the kool aide.

      By the way, I can swear and call names with the best of them too. A word of advice to you on the matter : you might be better of using the word "cunt" as it is widely considered to be the worst and most offensive in the English language, even more so that "fuck."

    6. Re:Minor niggles about MySQL AB by turgid · · Score: 1
      If I want to sell people some commercial software, or to give them some closed-source software, and provide them with MySQL as the accompanying database engine under the GPL, source and all (for MySQL) why the hell should I have to pay a single penny at all to MySQL?

      You should get a grip. You can't do this, since the MySQL client libraries are GPL. Your application would be in violation of the GPL.

      If you don't like it, write your own damn code or pony up the cash.

    7. Re:Minor niggles about MySQL AB by black+mariah · · Score: 0
      If you obtain something under the GPL, you retain the right to redistribute it under the GPL.
      Yes, I am thoroughly aware of this fact. However, when you purchase a commercial MySWL license, you are NOT puchasing a GPL'd version of the software.
      You are allowed to charge a reasonable fee for your time spend in copying it and for the medium upon which is is distributed.
      Again, I'm aware. Again, commercial MySQL IS NOT UNDER THE GPL.
      If I want to sell people some commercial software, or to give them some closed-source software, and provide them with MySQL as the accompanying database engine under the GPL, source and all (for MySQL) why the hell should I have to pay a single penny at all to MySQL?
      Because you need a commercial license to distribute MySQL in a commercial project. If you were to simply build some Free software and distribute with MySQL libraries, you are in the clear. You can not do the same thing with commercial products because, say it with me because I know you know it by now, COMMERCIAL MYSQL IS NOT UNDER THE GPL. Read this. If you still can't understand the concept of dual licensing, you're fucking hopeless.

      Funny, I always thought the most offensive phrase in the English language was 'trial lawyer'...
      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
  18. Software patents and the Fine Line by N3wsByt3 · · Score: 3, Interesting

    "There's a fine line that needs to be walked when it comes to software patents. Either extreme will stunt growth."

    Indeed, and that fine line is: allowing them.

    "On the one extreme[...]"

    sw patents are hopelessly borked. You can not patch the process up to be sure you only have high quality true software-innovations, and the whole idea of it is flawed in the first place, because software is akin to writing recipes, and it should be governed by copyright, not patents. and thirdly, patents are monopolies given by the state, because it is supposed to stimulate further innovation: all neutral research thusfar has indicated that it doesn't do that, on the contrary.

    "On the other extreme[...]"

    No, it won't. You seem to ignore the fact that, when software started with it's boom, there WERE NO sw patents. In fact, it can be reasonably argumented that it was just because they didn't existed at the time, that software knew such a high flight. Time and money isn't spend to produce new sw technologies; it is increasingly diverted to the legal departement of the companies. Companies that are flexible and can adapt will survive just fine without sw patents, rest assured.

    --
    --- "To pee or not to pee, that is the question." ---
  19. References? by Stone316 · · Score: 1

    Do you have any references to good reading material on how software patents hinder innovation? I don't know much about it and would like to read up on some of the arguments.. Specifically how do they hinder innovation?

    --
    "Thanks to the remote control I have the attention span of a gerbil."
  20. Summary by Anonymous Coward · · Score: 0

    Enterprise this Enterprise that.

    "We've been working with the enterprise market and getting ready for the enterprise market"

    "We deal a lot with enterprise customers"

  21. good! by N3wsByt3 · · Score: 1

    It's always nice to see ppl wanting to learn more.

    Anyway, there have been numerous posts in the past to it, but I don't know the links at heart. I do seem to remember the FFII has a page with links to sw-research, as does nosoftwarepatents.com, I think.

    Happy reading!

    --
    --- "To pee or not to pee, that is the question." ---
    1. Re:good! by Stone316 · · Score: 1

      I did a quick google and read a couple of articles which glossed over the topic but nothing indepth. I'll check them out, tnx.

      --
      "Thanks to the remote control I have the attention span of a gerbil."
  22. How about MySQL AB's interpretation of the GPL? by Anonymous Coward · · Score: 0
    How about MySQL AB's "interpretation" of the GPL? How will that harm the industry? Why have they chosen to "interpret" the GPL in this way? Since when did sending a query to a database equal linking to a library in terms of the GPL? Why must any application that uses MySQL be GPL unless a commercial license is obtained from MySQL AB?

    Why do people insist on using MySQL when far better superior alternatives such as PostgreSQL exist?

    1. Re:How about MySQL AB's interpretation of the GPL? by Anonymous Coward · · Score: 0

      > Why do people insist on using MySQL when far
      > better superior alternatives such as PostgreSQL
      > exist?

      Because, performancewise, 9 out of 10 British housewives couldn't tell the difference between Postgres and a dead crab. And some people want their data *this* week.

      > Why must any application that uses MySQL be GPL
      > unless a commercial license is obtained from
      > MySQL AB?

      Because it's their product, and they can sell it any way they like.

      Besides, if there are so many better alternatives that you're happier with, why should you care?

    2. Re:How about MySQL AB's interpretation of the GPL? by Anonymous Coward · · Score: 0
      Because it's their product, and they can sell it any way they like.

      And my point is, they like to make it available under the GPL and then sneakily try to extort money from people who are distributing it under the terms of the GPL through their "interpretation" of the GPL.

      Besides, if there are so many better alternatives that you're happier with, why should you care?

      I'm just upset because so many ignorant people have drunk the MySQL Kool Aide.

    3. Re:How about MySQL AB's interpretation of the GPL? by Anonymous Coward · · Score: 0

      > they like to make it available under the GPL and
      > then sneakily try to extort money from people
      > who are distributing it under the terms of the
      > GPL through their "interpretation" of the GPL.

      Their policy can be summed up as: "If you're Open Source, we're Open Source. If you're not Open Source, please see the nice people in Sales about buying a license."

      Pretty simple, really, and no "extortion" is involved. If you want to use MySQL software in an Open Source app, you can. If you want to keep the source closed, you still can use MySQL software -- you just have to pay for the privilege of doing so in that case.

    4. Re:How about MySQL AB's interpretation of the GPL? by jadavis · · Score: 1

      Their policy can be summed up as: "If you're Open Source, we're Open Source. If you're not Open Source, please see the nice people in Sales about buying a license."

      So long as your definition of "Open Source" does not include BSD or anything other than GPL.

      So it's more like: "If you're GPL, we're free. If you're BSD or anything else, see the nice people in sales.".

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    5. Re:How about MySQL AB's interpretation of the GPL? by SLi · · Score: 1

      That's just plainly incorrect. Your code only needs to be licensed under a GPL compatible license. And the BSD license (the newer revision without that nasty old advertising clause) is.

    6. Re:How about MySQL AB's interpretation of the GPL? by Anonymous Coward · · Score: 0
      Pretty simple, really, and no "extortion" is involved. If you want to use MySQL software in an Open Source app, you can. If you want to keep the source closed, you still can use MySQL software -- you just have to pay for the privilege of doing so in that case.

      That's completely missing my point. I'm talking about redistributing MySQL. They have one policy for some people, and another for everyone else.

      If you obtained MySQL under the terms of the GPL, surely you retain all the rights granted to you by the GPL? Where in the GPL does it say "but you must pay MySQL AB money to redistribute this software?"

    7. Re:How about MySQL AB's interpretation of the GPL? by Anonymous Coward · · Score: 0

      You are completely clueless. You can redistribute MySQL under the GPL. You just can't link it into $CLOSEDSRC program and redistribute it as GPL. Get a clue you luser.

    8. Re:How about MySQL AB's interpretation of the GPL? by arkanes · · Score: 1

      No, you're thinking in the wrong direction. A BSD app that's linked against GPL libraries can't be redistributed under the BSD license, and thus becomes de facto GPL. The BSD license is GPL-compatible, the GPL is not BSD-compatible.

    9. Re:How about MySQL AB's interpretation of the GPL? by SLi · · Score: 1

      Yes, I know that. But it's only de facto. You are still distributing your own code under the BSD license and the GPL code under GPL. Sounds actually very fair to me. It doesn't restrict at all how you can distribute your code as long as it's GPL compatible.

      Of course you can't just drop requirements from the GPL'd code and assume that after adding some BSD code you suddenly have more rights over that code, written by someone else...

    10. Re:How about MySQL AB's interpretation of the GPL? by arkanes · · Score: 1
      Well, no. If you write code under the BSD license, and then you merge that code with GPL code (by using the MySQL client libraries), then you can no longer distribute your code under the BSD license. Now, I'm not saying thats unfair or anything. But it's a fact. If you use GPL libraries, then your application will be distributed under the terms of the GPL. This is the viral part of the GPL in action.

      Once again, I don't think that's neccesarily bad or anything. But if you want to distribute under a BSD license, then you are, as a practical matter, prevented from using MySQL. It's the same thing if you want to distribute a closed source app too, of course, but I think this matters more to many people because the BSD license is also OSS (and thus "on the same side"), and also because the BSD license is often percieved as being "more free" - and thus, using MySQL with your BSD application would make it "less free".

    11. Re:How about MySQL AB's interpretation of the GPL? by SLi · · Score: 1

      Only if you intend to distribute under the BSD license without the source code, ie. closed source.

      In source form, the notion of "the entire work" will in this case be quite unimportant anyway, you do have the right to distribute your work under the BSD license and anyone can take that code and use it in ways that the BSDL allows (but GPL does not). If they want to go closed source, they can use a different DB or buy the commercial version of MySQL and use your product, entirely BSD licensed.

    12. Re:How about MySQL AB's interpretation of the GPL? by arkanes · · Score: 1

      You're missing the point. The people who recieve your product can not, as a practical matter, use it under the terms of the BSD license because it's tied to the GPL via the MySQL libraries. This is the case even if you support multiple back ends. This is exactly what people mean when they talk about the viral aspect of the GPL.

    13. Re:How about MySQL AB's interpretation of the GPL? by SLi · · Score: 1

      If you support multiple backends and you can at compile time disable linking MySQL in, the resulting binary is distributable without source.

  23. Valid points by Just+Some+Guy · · Score: 4, Insightful
    Why must any application that uses MySQL be GPL unless a commercial license is obtained from MySQL AB?

    If you're asking "what legal reason is there?", then the answer is because they decided in their infinite wisdom to GPL the client libraries, which is a more restrictive policy than any of the commercial DBs impose as far as I know.

    If you meant "why on Earth would they do that?", then I have no answer. They had to invent a stupid "FOSS License Exception" (see the above link for details) to allow popular non-GPL projects like PHP to offer MySQL support, and have basically removed any chance of commercial software support.

    In a nutshell, if you want to use a database in your non-GPL project (whether Free or proprietary) then MySQL is a poor choice. They've already added huge client library restrictions by moving from the LGPL to the GPL, and I don't see any reason to believe that they won't drop the "FOSS License Exception" kludge in the future. Note that I like the GPL - it's a good license and I support its goals - but this seems like a wholly inappropriate place to use it.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:Valid points by Anonymous Coward · · Score: 0

      If you're asking "what legal reason is there?", then the answer is because they decided in their infinite wisdom to GPL the client libraries [mysql.com], which is a more restrictive policy than any of the commercial DBs impose as far as I know.

      I am confused, maybe somebody who knows the law better can clarify this.

      Suppose I wrote an application that uses a database in MySQL, plus assorted other stuff I wrote in PHP/Java/Python/etc.

      The thing is I don't need to distribute the MySQL client, my customers can do that. Once that's in place, I can put everything else on top.

      Thus, nothing I did is restricted by GPL. Or am I completely off?

    2. Re:Valid points by Anonymous Coward · · Score: 0

      Linking to GPLed libraries counts as creating a derivative work, and thus the GPL applies just as if you'd used the code directly.

      See the GPL FAQ on this.

      This is also why a good number of libraries are released under the LGPL, which is basically GPL without this particular restriction. The GNU C libraries, on the other hand, use the GPL plus a special exception, which is even more liberal than the LGPL.

  24. Legal fees will fall? by ashitaka · · Score: 1

    (reads again...)

    Oh, never mind....

    --
    If you don't want to repeat the past, stop living in it.
  25. MySQL causing harm to web hosting by Frank+T.+Lofaro+Jr. · · Score: 1

    MySQL is so popular, that there are so many host that use it and don't offer PostgreSQL. They both are free, but PostgreSQL is better. Transactions, builtin programming language, GIS functions, extensibile types, etc.

    LAMP might be a cool acronym, but Linux + Apache + MySQL + PHP isn't the best. On an aside, embedding Perl in web pages might be better than the web page specific PHP.

    Here is to a new acronym: LAMP = Linux + Apache + Mod_perl + PostgreSQL.

    Happy Martin Luther King Day!

    --
    Just because it CAN be done, doesn't mean it should!
    1. Re:MySQL causing harm to web hosting by jadavis · · Score: 1

      [warning: blatant propoganda follows]

      Actually, it goes like this:

      "Build a brighter LAMP: Linux, Apache, Middleware, PostgreSQL"
      -- stolen (and probably butchered) from someone more clever than I.

      --
      Social scientists are inspired by theories; scientists are humbled by facts.
    2. Re:MySQL causing harm to web hosting by davegaramond · · Score: 1

      I don't see how the content of your post is an argument to "MySQL causing harm to *web hosting*". In fact, shared web hosting simply cannot use mod_perl due to the inability of mod_perl to prevent normal users from messing up Apache within their .htaccess files.

    3. Re:MySQL causing harm to web hosting by Anonymous Coward · · Score: 0

      Actually, on the contrary. MySQL gives web hosting industry a boon/boost by allowing people to write many database-backed web applications.

      From the view of the web hosting, it doesn't matter if the database is ACID or has advanced features. They don't write the application, they just provide the running daemon.

      The things that matter are: a) it's fast (and thus doesn't consume too much server resources); b) it's stable (doesn't crashes a lot, doesn't need to be monitored or restarted every now and then); c) free (no licensing cost); d) it can be secured (so a user can't freely access another user's database); e) easy to use (doesn't cause too much support burden). MySQL fulfills all those requirements.

    4. Re:MySQL causing harm to web hosting by Frank+T.+Lofaro+Jr. · · Score: 1

      Try to find a web host the offers PostgreSQL. Most do not. Most do offer MySQL if they are UNIX based.

      If it weren't for MySQL, many of the MySQL only web hosts would use PostgreSQL.

      Hence the harm.

      Something which is seen as "good enough" forces out something that would be better.

      --
      Just because it CAN be done, doesn't mean it should!
    5. Re:MySQL causing harm to web hosting by Anonymous Coward · · Score: 0

      Yes, most web hosting firms do not provide pg servers and it is probably somewhat a function of what you just described... pg has more features and is more likely to weigh down their shared hosting server. mySQL is fast, simple, the most popular database for web hosting applications, lightweight (depending on what you compare it to), and it does scale pretty well.

      Even though the market for open source databases has already made its choice between the two, some people will not let it go.

      Furthermore... you decry that LAMP is not the best... but you don't say which application it isn't best for. Have you ever considered that there isn't ONE RIGHT ANSWER and that sometimes some tools are better for one job than another?

  26. How does he get paid? by MBraynard · · Score: 1

    I'm wondering how does someone who is 'ceo' of something that is totally free make money. Service contracts? My host provides free service/consulting for MySQL (icdsoft.com). And besides, it ain't rocket science.

    1. Re:How does he get paid? by jbplou · · Score: 1

      Service contracts is a major way. You sited a web host I'm sure icdsoft.com has a service contract with someone to fix problems(unless they are a reseller of hosting). Mid-Large Businesses and governement agencies all need service contracts for help or they won't use a software package for the most part. Plus if you look at mysql.com you'll notice they also over consulting and training.

    2. Re:How does he get paid? by MBraynard · · Score: 1
      Hiya, I guess this makes sense. The problem, however, is that when you have a free-as-in-beer product and it is OSS, you do not have an exclusivity on training or service contracts.

      In fact, you may be at a disadvantage in that other companies can focus solely on support or training, while you have the added burden of development. While true that you might be the company that knows the software best, like I said before - it isn't rocket science.

  27. MOD UP! Re:Minor niggles about MySQL AB by wolrahnaes · · Score: 1

    Parent was the funniest thing I've read on /. in a while!

    --
    I used to get high on life, but I developed a tolerance. Now I need something stronger.