Slashdot Mirror


CA Advantage Ingres To Be Released As Open Source

Bruce Perens writes "Computer Associates is releasing CA Advantage Ingres as Open Source under a variant of the Common Public License. The press release is here. This is a commercial fork of the public-domain University Ingres of the '80's, probably the first real relational database. CA's product added SQL and in general brought the program up to enterprise quality. So has the PostgreSQL project. It will be interesting to see if there can be any synergies between the two products. The BSD licensing on PostgreSQL would allow it." Here's an article at CRN on this and a few other open source moves announced today by CA; can anyone find a link to the text of CA's "Trusted Open Source License"? Related news, contributed by an semi-anonymous reader, is that CA has established "a new open-source foundation that will support Plone, the content management system built on the free Zope Application server," and that Plone's license will change as a result.

217 comments

  1. Lifecycle of Bad Software by Anonymous Coward · · Score: 4, Funny

    1. Create bad design

    2. Create bad software

    3. Sell zero copies

    4. Release as "open source" to get attention

    5. No Profit!!

    1. Re:Lifecycle of Bad Software by BiggySmallz · · Score: 5, Informative

      This parent post is indeed flamebait, but it very accurately describes the life-cycle of Ingres. I worked for several years at CA, and everybody, internally and externally, knew what a boatload of crap Ingres was. Most of our products were written to SQL Server, although Ingres was free to integrate in, since no one would go near the crap.

    2. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 1, Informative

      Speaking as the Systems manager of an organisation that uses Ingres, I can quite happily state that many people use Ingres and love it.

      Specifically those organisations that don't need all the bundleware supplied with products like Oracle or SQL server, and can't afford a fulltime DBA onsite.

      Ingres performs extremely well as a zero maintenance embedded full-function SQL database, and many of those traits carry over into more general purpose uses.

      If you're looking for a good, strong, reliable, low overhead SQL database server for a SME deployment, you would be well advised to look closely at Ingres.

      No matter what happens with the Open Source fork of Ingres, the money spent on support with Computer Associates for those rare occasions where you need expert assistance is money well spent. Their staff are professional, literate, punctual, and very client focussed - and this is the manufacturer.

    3. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      " Speaking as the Systems manager "

      Well, speaking as a manager of systems managers, I can say that 3 years of experience doesn't make you much of an expert in managing systems (whatever that means).

      And if you have more than 3 years, keep it to yourself.

    4. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      Something tells me that you probably work for JBoss... uhh.. I mean Computer Associates.

    5. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      Liar!... Ingres RULEZ!!!

    6. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      Bah!... Ingres SUX0RZ!!!

    7. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      Informative? Mod this trash down -- this guy is obviously a has-been that hasn't worked with or known the software for years.

      CA has changed alot in recent years. So what if you knew somebody that didn't like ingres half a decade ago. Nowadays they are a very decent company to work with..

    8. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      You forgot that CA picked it up at almost step 3. The aquired everything they have...

    9. Re:Lifecycle of Bad Software by Anonymous Coward · · Score: 0

      I once worked there too a long while back, but I had no probs with Ingres.... only with the raises.

    10. Re:Lifecycle of Bad Software by BiggySmallz · · Score: 1

      Well I was there in the early to mid '90s, and I don't remember exactly what everyone thought, but I know a good amount weren't that thrilled with it. It did work though and apparently some customers did use it with good results. I do recall one or two fans too.

      Btw, don't get so touchy... I didn't say it was any worse than the other alternitives (don't get me start on some of the others).

  2. intelligence by antimatt · · Score: 0

    Going open-source is the smart move, no matter what the software may do. Ingres is buggy just like any other first release. Open-source makes it attractive to us nerds, and the wider the user base, the greater the number of users who can manipulate the software, and the faster the bugs disappear.

    1. Re:intelligence by kasin · · Score: 4, Interesting

      First release? Ingres has been around for quite a while. We have used ingres as a commercial product for a decade. Not to say it doesn't have bugs though.

    2. Re:intelligence by antimatt · · Score: 5, Funny

      you and your "logic" and your "knowledge" of "computers" and "stuff."

  3. Oracle was the first SQL relational database .... by molarmass192 · · Score: 4, Informative

    At least so far as commercial products go, Oracle was the first. To save a click, Oracle V1 was a consulting project used solely by CIA and dating back to 1978. Oracle V2 was the first marketed version starting in 1980.

    --

    Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
  4. So many oss/fsf RDBMS... by Ianoo · · Score: 5, Interesting

    MySQL, PostgreSQL, Firebird, now "Ingres". I guess it's better than having none, but it's becoming a pain to support the perculiarities of each of these products in, for example, a PHP script intended for general use, which you want to make work with as many different database systems as possible. It's a pity each of them aren't more compliant with the now 12 year old SQL-92 standard or the now 5 year old SQL-99 standard.

    1. Re:So many oss/fsf RDBMS... by sholden · · Score: 1, Insightful

      You use a non-toy language which abstracts out the peculiarities of those databases.

      "use DBI;" and all those databases work.

    2. Re:So many oss/fsf RDBMS... by MisterFancypants · · Score: 2, Insightful

      You use a non-toy language which abstracts out the peculiarities of those databases.
      "use DBI;" and all those databases work.

      What if you're creating a 'non-toy' database application. Do you really think DBI abstracts the differences in all of these databases, even when using triggers, etc, to the point where you don't have to worry about it? Uh.. No.
    3. Re:So many oss/fsf RDBMS... by lpontiac · · Score: 1
      but it's becoming a pain to support the perculiarities of each of these products in, for example, a PHP script intended for general use, which you want to make work with as many different database systems as possible.

      So don't.

      The database exists to support the application, not the other way around.

    4. Re:So many oss/fsf RDBMS... by Uruk · · Score: 1

      That's the great thing about standards. There are so many of them to choose from. :) The thing with freedom of choice in software is that it tends to spread things out like this. (For example, there are several different popular choices for desktop environments) That's not without its own advantages, but it kinda sucks for the developers. I can't blame the developers of the packages though from doing things that are non-standard; they're just trying to distinguish themselves, and there is so much else that is possible on top of the standard that they shouldn't even restrict themselves to it.

      I've always thought that the database is a mature and old enough technology that it should pretty much be a standard component of an OS, like filesystems and perhaps windowing systems. Think about how easy it would be to organize configurations, replacing both UNIX-style /etc/foo and the windows registry. Or how it could be used as a standardized store by applications for things like email, multimedia files, and just about anything.

      As for ingres, I say it sounds great. More open code provides:
      - more study opportunity for university classes,
      - more sample code for hackers learning,
      - more opportunities for third parties that need to bundle software

      It's a win for everybody as far as I'm concerned.

      --
      -- Truth goes out the door when rumor comes innuendo. -- Groucho Marx
    5. Re:So many oss/fsf RDBMS... by sholden · · Score: 1

      Then clearly you pick the database which gives you want you need and code for it. If you want to support more than one you write your application specific abstraction layer - which will be done with far less code than would be needed without the DBI abstraction layer.

      A non-toy application doesn't have to run with every open source database engine that happens to exist this week.

    6. Re:So many oss/fsf RDBMS... by Tablizer · · Score: 1

      You use a non-toy language which abstracts out the peculiarities of those databases.

      Another language that claims to do that is HQL. However, I am skeptical that it can capture all the peculiarities of the different SQL dialects. Settling for a lowest-common-denoninator query language is not very satisfying.

    7. Re:So many oss/fsf RDBMS... by darnok · · Score: 1

      Without wanting to be nasty, I'd say from a FOSS perspective you'd probably focus on:
      - MySQL (because it's so ubiquitous, fast and solid, although missing some features that would make it a better fit for some uses)
      - Postgres (because it's mature, reasonably fast, solid, been available for a while and broadly comparable with Oracle, SQL Server and DB2 in terms of capability)
      - Oracle/DB2/SQL Server (subject to whether you wanted to deal with commercial databases or not) ...and that's about it.

      Other, totally viable, databases options exist, but unless you're particularly enamoured with e.g. SAP DB, I'd say you'd probably be better off leaving support of such products to the one or two users who really want to use them. I'm assuming GPL here - supposedly development is shared between "owners" and users, with users kicking their enhancements back to the base product for inclusion.

    8. Re:So many oss/fsf RDBMS... by KingOfBLASH · · Score: 4, Interesting

      The DBI in Perl is a way to access all types of database using the same Perl functions -- i.e. so you don't have to remember how to execute SQL on a MySQL database, Postgresql, Oracle, etc., like in PHP -- because in languages like PHP they all use different functions. However, you still have to send SQL to the database and that SQL has to come back. To my knowledge, no one has implemented a DBI wrapper to transform SQL so that it confirms to each databases peculiarities.

    9. Re:So many oss/fsf RDBMS... by afidel · · Score: 1

      How about write to the SQL99 standard and have database specific modules while overloads functions which rely on DB specific functionality. This way your design is naturally modular and abstracted. If you design like this problems porting will be greatly minimized. Don't say it can't be done because I did it for a freaking interpreted game engine (NWN) in a C like language, doing it with a real language should be at least twice as easy.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    10. Re:So many oss/fsf RDBMS... by veg_all · · Score: 2, Insightful

      What I want to know is: What do you have against toys? Scared by a clown as a child?

      Even on the big, bad interweb, sometimes one doesn't feel like writing "production" "code." Sometimes one may just want to make amusing and useful applications that need to manage fair amounts of data. And then one might want to share them with others.

      Sheesh. People here can get so serious about computers. Coding is such a manly art!

      --
      grammar-lesson free since 1999. (rescinded - 2005)
    11. Re:So many oss/fsf RDBMS... by darnok · · Score: 1

      Yep, that's a good approach, provided you're prepared to write a good deal of code in your abstraction layer to support MySQL's "differences" compared to other database products.

      On the other hand, if MySQL is going to be 50%+ of your user base, then it might not be the worth the effort.

    12. Re:So many oss/fsf RDBMS... by sholden · · Score: 1

      DBI handles the trivial stuff like what needs to be quoted.

      Differing SQL dialects are another matter, but for the *vast* majority of stuff you don't use anything but simple selects and simple inserts.

      If you do anything more complicated you need to do some work, it's not after all magic. Then again the last perl program I moved from mysql to postgresql needed a one line change to make it work (using a case-insensitive hash for results) - though the fact that the database stuff was all in Database.pm probably had a lot to do with that (rather than having SQL scattered in random locations throughout the 10000 lines of code.

      I'm willing to bet that any code whose author thinks "oh look a new opensource database I better make it work with that just in case someone cares" isn't doing anything other than simple inserts and selects, maybe with an update or delete somewhere...

      For more database feature using programs the database tends to be as fundamental a design choice as the implementation language, at least it should be. Of course sometimes the decision is to place all the logic in the code and use the database as a simple storage area (maybe the decrepid database server is overloaded and ...slow...) which makes for relatively database neutral code.

    13. Re:So many oss/fsf RDBMS... by hendridm · · Score: 1

      Pfft. There are many good abstraction classes available for PHP, including the excellent ADOdb. Sadly, Ingres isn't on the list, but it looks like pretty much everything else is.

    14. Re:So many oss/fsf RDBMS... by Ianoo · · Score: 1

      You've obviously never programmed a powerful database application in something like J2EE/JDBC (which has the same problems with differing SQL syntax as PHP, just a unified set of classes and methods). I certainly find I need complex joins to do any kind of data access, LEFT JOIN being extremely useful and not universal. The table creation syntax and data types also differ which can make a difference when trying to optimise storage efficiency.

    15. Re:So many oss/fsf RDBMS... by AJWM · · Score: 2, Informative

      so you don't have to remember how to execute SQL on a MySQL database, Postgresql, Oracle, etc., like in PHP -- because in languages like PHP they all use different functions.

      Um, do you have something against the Pear DB package and putting "require_once 'DB.php';" in your PHP code?

      --
      -- Alastair
    16. Re:So many oss/fsf RDBMS... by Anonymous Coward · · Score: 0

      The Windows registry is a database. And there's no clear advantage to using a relational database for general-purpose files. That's what filesystems are designed for.

    17. Re:So many oss/fsf RDBMS... by Dom2 · · Score: 1
      Surely that's what database views are for solving? Oh, that kind of excludes MySQL. Oops.

      -Dom

    18. Re:So many oss/fsf RDBMS... by joib · · Score: 4, Informative


      It's a pity each of them aren't more compliant with the now 12 year old SQL-92 standard or the now 5 year old SQL-99 standard.


      Not to mention the brand spanking new SQL:2003 standard, see e.g. this overview of the new features.

    19. Re:So many oss/fsf RDBMS... by robin · · Score: 1

      For transmogrifying dialects of SQL, see http://sqlfairy.sf.net/ (plus bonus visualisation tools, and an all time great logo to boot)

      --
      W.A.S.T.E.
    20. Re:So many oss/fsf RDBMS... by robin · · Score: 1

      Sorry for replying to myself here -- SQL fairy won't help with the different outer join syntax, for the moment it's only DDL.

      --
      W.A.S.T.E.
    21. Re:So many oss/fsf RDBMS... by Brother52 · · Score: 2, Insightful
      a pain to support the perculiarities of each of these products in, for example, a PHP script intended for general use

      It's more a problem with PHP than with anything else - failure to have a unified DBMS driver as about every other scripting language does.

    22. Re:So many oss/fsf RDBMS... by BarryNorton · · Score: 2, Funny

      I think you're missing the most important issue - the logo! ROFL

    23. Re:So many oss/fsf RDBMS... by Anonymous Coward · · Score: 0

      No, but most PHP developers seem not to use it. PHP developers also seem to ignore Smarty and other tools used to implement MVC patterns and other best practices.

    24. Re:So many oss/fsf RDBMS... by leandrod · · Score: 1

      There is no free software RDBMS. The only current RDBMS is Alphora Dataphor, but it is not free. Remember, SQL is not conformant to the Relational Model.

      Ingres did have a relational interface, QUEL. I haven't been able to discover if QUEL is still supported, but even if it is and if it was not corrupted, Ingres wouldn't be an RDBMS because SQL access to data violates the RM.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    25. Re:So many oss/fsf RDBMS... by leandrod · · Score: 1
      > from a FOSS perspective you'd probably focus on: [...] Oracle/DB2/SQL Server

      No, none of these are free software. In dealing with commercial DBMSs, you'd focus on MaxDB (SAPdb), CA Ingres or PostgreSQL, all being free software too.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    26. Re:So many oss/fsf RDBMS... by javax · · Score: 1

      How about just using in-database functions? With this there will be no 'incompatible' code inside your python/php/perl/java/... application - just use the right database driver and off you go.
      Of course you still have to code the in-database functions for each supported database.

    27. Re:So many oss/fsf RDBMS... by KingOfBLASH · · Score: 1
      One word:
      AUTO_INCREMENT
      . Try using that on a Postgresql database and it will break (or any database that supports the SQL standard). So you're right if you're talking about very simple stuff, but not for any serious programming.
    28. Re:So many oss/fsf RDBMS... by KingOfBLASH · · Score: 1

      No, actually I use Pear DB when I can, but I've had to make things work on client machines before which didn't have pear available but wanted the database work in PHP. So in the end I had to go back to calling mysql_connect() etc. as if Pear DB didn't exist. And, no, reconfiguring their server wasn't an option.

    29. Re:So many oss/fsf RDBMS... by Baki · · Score: 1

      Hmm, at first I thought the date of the sql:2003 std. paper was april 1st, but it is march 1st. It is quite amusing: partly it consists of stuff already in oracle for years, partly it is actually useful (the multiset and casting types, also already possible in oracle by the way) and the rest is crap (the create table 'like' for example).

      Hard to believe that this is an official sql standard.

    30. Re:So many oss/fsf RDBMS... by Anonymous Coward · · Score: 0

      And you left out SAPdb...

    31. Re:So many oss/fsf RDBMS... by sholden · · Score: 1

      The mysql->postgres I did used autoincrement and worked fine thanks...

      A sequence works just fine. There's even the serial "type" which does the sequence creation for you.

    32. Re:So many oss/fsf RDBMS... by sholden · · Score: 1

      Did you manage to miss the bit where I mentioned more complicated database applications. You know the bit where I said that the choice of database they use is just as fundamental as choice of implementation language.

      You don't expect such an application to just work with every database engine you throw at it. You design for the engine you are using, and the features it has (in a perfect world you choose the engine based upon the features you need).

      However, the *vast* majority of database using programs are not like that, they use trivial operations in which a simple join is a rarity.

      Take mysql as an example. An extremely popular database choice, do you really think most people are doing complex joins with it? Or do you think they are storing blog entries in a table with about five fields and comments in another table with about five fields and probably not bothering with a join?

      I know what I think is the most common usage. Especially amongst the "oh a new open source database, better make the program work with it too" crowd.

      But no I haven't done J2EE/JDBC, I have however done a fair bit of Sybase crap but that was a long time ago and I'd rather keep the memories repressed.

    33. Re:So many oss/fsf RDBMS... by robin · · Score: 1

      I think you're missing the comment where I said they had an "all time great logo"

      --
      W.A.S.T.E.
    34. Re:So many oss/fsf RDBMS... by BarryNorton · · Score: 1

      *Ulp* fair point - I'd forgotten that you'd replied to yourself while I went to visit the page... so you see it's your fault really! ;) (jk, I take this on the chin really...)

    35. Re:So many oss/fsf RDBMS... by KingOfBLASH · · Score: 1

      Hmmm...they must have changed it. I can remember a time not so long ago where AUTO_INCREMENT didn't work under Postgres. Regardless, there are plenty of other examples of things you can do under Postgres that you can't under MySQL which would be a problem...

  5. Why not PostgreSQL? by RuneB · · Score: 3, Insightful

    Why would someone want to use this instead of PostgreSQL?

    --
    dtach - A tiny program that emulates the detach feat
    1. Re:Why not PostgreSQL? by molarmass192 · · Score: 3, Insightful

      The only reason I can think is that Ingres was at one time one of the big 4, namely Oracle, Sybase, DB2, and Ingres. It comes from a commercial heritage, so it might be an easier sell to Joe CIO?

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    2. Re:Why not PostgreSQL? by Anonymous Coward · · Score: 5, Insightful

      You wouldn't. The source code is so that existing legacy customers can fix their own bugs.

    3. Re:Why not PostgreSQL? by Nutria · · Score: 2, Interesting
      Postgres does ACID-compliant transactions and is much faster and more scalable than Ingres, and actually supports SQL-92, and triggers, and stored procs, and many many other modern features.

      Because PostgreSQL doesn't have PITR, so fails the "Durability" portion of ACID.

      I'd never run a mission-critical DB off an RDBMS that isn't fully ACID. Yes, I'm anal that way, but that's what happens after you've worked with a real RDBMS running on a great OS for a while.

      --
      "I don't know, therefore Aliens" Wafflebox1
    4. Re:Why not PostgreSQL? by Twirlip+of+the+Mists · · Score: 4, Funny

      Because "Ingres" is easy to pronounce?

      (Okay, on preview I realize that it's not actually easy to pronounce at all unless you too an art appreciation class in college. It's "On-gur." Oh, well. It's still easier to pronounce than PostgreSQL, which despite being my favorite database I can't tell anybody about because I can't say the damn name without feeling like a moron.)

      --

      I write in my journal
    5. Re:Why not PostgreSQL? by crimbil · · Score: 2, Informative

      Because quite a few of CA's products use either Ingres or MS SQL. With CA releasing more apps which can be hosted on linux as well as firms which use Windows but don't want to pay for MS SQL, more people are using Ingres. So, by going open source, that relieves some of the load on internal developers. I suppose it could also be argued that now Ingres will be improved without CA having to pay for more programmers.

    6. Re:Why not PostgreSQL? by Ianoo · · Score: 1

      Are you sure it's French? I would have just pronounced it "In-Gress" unless told otherwise. For the record, PostgreSQL is pronounced Post-Gress-Queue-El.

    7. Re:Why not PostgreSQL? by Tyler+Eaves · · Score: 1

      Ever considered that just having a 'gres' doesn't make it French?

      Ingres rhymes with In-gress

      PostgreSQL is post-gres-que-el

      --
      TODO: Something witty here...
    8. Re:Why not PostgreSQL? by brank · · Score: 3, Informative

      Ingres is a backronym for "Interactive Graphics REtrieval System" (the task from which Stonebraker got his original funding). It was named after French painter Jean Auguste Dominique Ingres.

      --
      it's green.
    9. Re:Why not PostgreSQL? by Anonymous Coward · · Score: 0

      PostgreSQL is based on Ingres, no?

    10. Re:Why not PostgreSQL? by HeadDown · · Score: 2, Insightful

      Because it might have better Windows support than PostgreSQL. I'm looking forward to giving it a whirl.

    11. Re:Why not PostgreSQL? by marco_craveiro · · Score: 1

      what are your problems exactly? i used the cygwin version of postgres in production without any problems... and the native should be out soon, IIRC...

    12. Re:Why not PostgreSQL? by hey+hey+hey · · Score: 2, Insightful

      The source base diverged over 20 years ago. I don't think there will be much in common anymore.

    13. Re:Why not PostgreSQL? by HeadDown · · Score: 2, Informative
      My problems are that I can't inflict the cygwin installer on my clients, and that the PostgreSQL on Windows HOWTO specifically states
      That being all said and done however, we don't recommend using the cygwin version of PostgreSQL for "Production" quality databases, nor high load levels. The cygwin emulation layer introduces a few limitations, namely the lack of being able to tune PostgreSQL to the same performance levels of a Unix system, and we're also not sure how well the data integrity features of Windows + cygwin + PostgreSQL work in the event of a system crash, hardware failure, etc.

      Regarding native Windows PostgreSQL, it seems like it's going to be out 'soon' pretty much as long as I can remember. I'm sure it'll happen sometime, but I'm not holding my breath. Even when it does happen, it'll be very new to the platform.

    14. Re:Why not PostgreSQL? by tehcyder · · Score: 1
      More like "Ang'rrr" isn't it?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    15. Re:Why not PostgreSQL? by gerbouille · · Score: 1

      Sorry, I don't think there is an equivalent sound in english for "Ingres". Try somethinq between "On-Gre" and "Inn-Gre", but with no "S" (the final "S" is never pronounced in French).

      --
      This post is displayed with recycled electrons
    16. Re:Why not PostgreSQL? by Anonymous Coward · · Score: 0

      Ingres was never part of the big four, I think Informix was a bigger name than Ingres.

    17. Re:Why not PostgreSQL? by bartwol · · Score: 1
      Yep...Informix was the fourth.

      <bart

    18. Re:Why not PostgreSQL? by Anonymous Coward · · Score: 0

      " Regarding native Windows PostgreSQL, it seems like it's going to be out 'soon' pretty much as long as I can remember. I'm sure it'll happen sometime, but I'm not holding my breath. Even when it does happen, it'll be very new to the platform. "

      This is kind of funny, though it is worth mentioning that postgres 7.5 cvs actually can be compiled on windows, and there are alpha builds for windows available for those willing...

      The thing about postgres on windows and production use is that many developers will never be eager to run it on windows simply becuase windows is such an inferior os to *nix... so why recommend it? Especially since postgres trys to work with the computers OS and not as a replacement for it. I'll grant that other db's try to cater to windows but thats only cause they have commercial intrests pushing them hard in that direction...

    19. Re:Why not PostgreSQL? by Twirlip+of+the+Mists · · Score: 1

      Ever considered that just having a 'gres' doesn't make it French?

      Being named after an incredibly well-know French painter of the 19th century, on the other hand, does.

      PostgreSQL is post-gres-que-el

      Hence the part where I feel like a moron. Great database; dumb name.

      --

      I write in my journal
    20. Re:Why not PostgreSQL? by leandrod · · Score: 1
      > PostgreSQL doesn't have PITR, so fails the "Durability" portion of ACID.

      Can you expand on this? Like URLs documenting it?

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    21. Re:Why not PostgreSQL? by leandrod · · Score: 1
      > Why would someone want to use this instead

      Because Ingres still supports a relational language, QUEL.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    22. Re:Why not PostgreSQL? by johnnyb · · Score: 1

      PITR is not a requirement of "durability". ACID, as far as I'm aware, does not include what happens if your data center goes up in a ball of flames, only what happens if your computer crashes.

      In that case, PG is perfectly durable, using write-ahead logging. You can shut off your computer at any time and the result will be a sane dataset, with all committed transactions intact.

    23. Re:Why not PostgreSQL? by generic-man · · Score: 1

      When I worked for Computer Associates, everyone there pronounced it as "ing-gress."

      --
      For more information, click here.
    24. Re:Why not PostgreSQL? by molarmass192 · · Score: 1

      Yep, that's right, my bad (it's been a long time) ... Informix was based on the Ingres codebase, not vice-versa.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    25. Re:Why not PostgreSQL? by Tukla · · Score: 1

      It doesn't support Pain in the Rear?

  6. MYSQL by Anonymous Coward · · Score: 4, Insightful

    With all the quality open-source RDBMS's like Postgres, Firebird and now Ingres why the hell would anybody, ANYBODY want to use a hacked up beast like MYSQL for heavy database work. MYSQL was beautiful when it was used for what it was designed for. At some point, the developers gave in to user demands to start adding in RDBMS functionality, and now its a multiheaded beast. Sad.

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

      Ease of use, maybe? MySQL is far simpler to use than any of the products you just mentioned.

    2. Re:MYSQL by Anonymous Coward · · Score: 1, Insightful

      Ok, true, but if the problem you are trying to solve requires features like referential integrity, then its time to move up to a real (read: designed for the purpose) database. Besides, IMHO, Firebird is simpler to use than MYSQL.

    3. Re:MYSQL by NonSequor · · Score: 1

      Several years ago I was able to set up PostgreSQL fairly easily (and securely since I only accepted connections from localhost) with no prior experience. As far as I can tell, the complexity of setup issue is overblown.

      --
      My only political goal is to see to it that no political party achieves its goals.
    4. Re:MYSQL by sapbasisnerd · · Score: 1

      Which may be a big part of why MySQL bought SAPDB now MAXDB from SAP.

    5. Re:MYSQL by hendridm · · Score: 3, Insightful

      This is Slashdot, where PHP, MySQL, and Visual Basic are "toy" applications. PHP is awesome and getting better all the time. Is it the killer language that will devour all others? Hell no, but my clients don't seem to care as long as their sites are running. MySQL is the backend on them all, too. Works great for what they need. Is Visual Basic toxic waste that causes new programmers to forever learn how to code the wrong way? Yes, but it seems to do okay for RAD at my current employer. Yeah, the apps would be cool if they were in C++, but it isn't necessary for nearly all the apps the employees use.

      Use the right tool for the job! Sometimes standards are more important than cutting edge. Would I like to upgrade our web server to something less loathsome than ASP and FrontPage extensions? Hell yes! But transition takes time, especially in a zero-budget bureaucracy...

    6. Re:MYSQL by joib · · Score: 5, Informative


      MySQL is the backend on them all, too. Works great for what they need.


      Good for you. Frankly, I think that in many cases the features of MySQL would be enough for me too. Now let me explain why I prefer PostgreSQL:

      1. I've used both, and IMHO both are about equally easy to use. So at least for me, the often made claim that MySQL is easier to use is bollocks.

      2. I don't run the DB on Windows, so the fact that MySQL has a native Windows port and PostgreSQL hasn't, doesn't bother me. If you care, the next PostgreSQL release is supposed to include a native Windows version.

      3. The PostgreSQL client libraries are BSD, while the MySQL libraries are GPL. If I make commercial apps, I would have to buy a commercial license from MySQL Ab.

      4. MySQL is often supposed to have superior performance compared to PostgreSQL in the case of a single user doing simple queries. But IMHO this doesn't really matter, since in almost all cases a single user doing simple queries means a simple application, where any low end PC provides enough juice. Where performance matters is a situation with many users doing complicated queries (including writes as well as reads), a situation that PostgreSQL handles much better than MySQL.

      5. Features. The PostgreSQL query language supports a much larger subset of the latest SQL standard (SQL:2003) than MySQL. If I find that I need some specific feature, it is quite probable that it exists in PostgreSQL but not in MySQL. Such as subselects, how can you live without them?
      And no, beta versions of MySQL don't count. Or stored procedures.

      6. ACID properties, something that the PostgreSQL development team takes very seriously. E.g. does MySQL check foreign key constraints, or are they still no-ops?

      In short, I feel that MySQL provides no benefit compared to PostgreSQL at the low end (such as ease of use etc.), and if you need more high-end features you'll run out of steam with MySQL way before PostgreSQL does.

    7. Re:MYSQL by MattRog · · Score: 1

      The point is not whether or not you can accomplish something using MySQL. The point is that it takes more effort on your part to do it right. If you were my employee I'd want you to do it right in the shortest amount of time. MySQL forces you to spend more time to do it wrong.

      For example:
      *Before MySQL implemented foreign key constraints you had to manually run queries to ensure that the parent(s) existed (this is still a problem if you do not use InnoDB)
      *Since MySQL lacks more complex constraints you must implement business rules procedurally in your code. This is less simple (and therefore less desirable) than declarative constraints in the DBMS and is also easily circumvented (possibly leading to inconsistent e.g. worthless data)
      *Since MySQL lacks stored procedures and triggers you must implement these in code (same caveats apply as above)
      *Since MySQL (except the latest versions) does not support multi-table updates/deletes you must implement this in code
      *Since MySQL does not support views then underlying schema changes are exposed to applications and so you must change the application (this is bad for obvious reasons).

      And there are plenty of other reasons which make it more difficult, more time consuming, and flat out more dangerous to develop MySQL applications (from a data integrity standpoint). Of course, MySQL is still better than rolling your own DBMS (e.g XML or something) so between nothing and MySQL, MySQL still wins. But between more capable DBMS products MySQL causes nothing but more work for developers.

      "Use the right tool for the job!"
      This is more a commentary on the state of the IT industry than a pointed reply to your comment but most people that say this do not know how to select the "right tool". They lack the fundamentals and critical thinking skills to do so. They merely know tools and how to mechanically apply them ("When you have a hammer every problem looks like a nail").

      --

      Thanks,
      --
      Matt
    8. Re:MYSQL by danharan · · Score: 2, Interesting

      The only reason I started with MySQL instead of PG was because of the windows installer, or more specifically PHPTriad.

      After mucking around in Oracle and PL/SQL for a year and reading about db normalization, going back to PHP was fairly traumatic. There's no way you can build enterprise-scale apps with that toy. No sub-selects or transaction support? Eek!

      I'm eagerly waiting for PG's native windows install, and re-writing all my queries to standard SQL, erasing hundreds of line of code that hacked around MySQL's lack of features.

      Anyhow, main reason I wanted to respond- I did no know or think to find out what the license was for PG's client libraries. You just gave me another reason to switch, and one that can be convincing to management. Thanks! :)

      --
      Information: "I want to be anthropomorphized"
    9. Re:MYSQL by ninejaguar · · Score: 1
      3. The PostgreSQL client libraries are BSD, while the MySQL libraries are GPL. If I make commercial apps, I would have to buy a commercial license from MySQL Ab.

      I have to clarify something that others may misunderstand in your list.

      I believe you meant to say, "If I make proprietary apps". There are plenty of non-proprietary commercial apps out there that are Open Sourced (even GPL'd): RedHat Linux, FireBird, MySQL, PostgreSQL, and now Ingres.

      = 9J =

    10. Re:MYSQL by Tukla · · Score: 1
      How is MySQL easier to use?

      Please note that I don't use either product (I prefer McKoi or plain Berkeley DB), so this isn't meant as flamebait. It's just that I keep hearing this claim repeated in every database shootout, but nobody ever expands on it.

  7. Plone license by polin8 · · Score: 4, Informative
    from the Plone Foundation Faq
    Will Plone still be Open Source?

    Absolutely. Plone will be issued under an OSI-approved license. The Foundation is working to build a guarantee of this nature in to the Foundation bylaws and in the contributor agreement."

    Will Plone will also be released under a non-GPL (or non-Open Source) license?

    The current Plone approach states that companies can negotiate a non-GPL license. Thus, the Foundation might pursue a dual-licensing (GPL and non-GPL) scheme -- but, at this time, the Board has not yet created any policies on this. This is an important question for the community, of course, and the Foundation intends to have this conversation in a transparent way. For more information, see Contributor's Agreement for Plone Explained.

    1. Re:Plone license by Gaetano · · Score: 1

      If I had mod points I would mod this post back up. Clearly this is not Offtopic as it cleared up something that the article clearly got wrong regaurding plone no longer being under the GPL.

      Somone please mod this post back up as informative!

    2. Re:Plone license by drmike0099 · · Score: 2, Insightful

      Is anyone else a little bit disturbed by this change in licensing? Perhaps it was the CA guy referring to the GPL as "viral" in the article, or perhaps it was that they went out of the way to reassure us that nothing "sinister" was going on. Maybe it's the fact that they are coming up with (yet another) open source license, which typically means they have some hokey rule in there that fits the OSI's definition legally, but not in spirit.

      I could definitely be considered paranoid, but they could have easily dual-licensed it as GPL and something else (which they state above in the FAQ) without coming across as a little sinister, but nowhere in the article do they mention dual-licensing w/ GPL. Add that to the "viral" comment and some of the other stuff they said, and I don't think the open source license will wind up being as good as you might think. Time to fork Plone? (j/k) I hope that I'm proven to simply be a bit jumpy, and not actually right...

    3. Re:Plone license by Anonymous Coward · · Score: 0

      why fork it? simply move to better (and related) technology: zope 3.

    4. Re:Plone license by polin8 · · Score: 1

      I think the biggest problem was that the news came from CA, not from the Plone Foundation. CA jumped the gun.

      The other concern is that according to the article CA plans to release a Plone based product on Monday, but they don't want to release the source. As of now, Plone is GPL only, iirc. It seems that CA may have trouble getting a license they like by this weeken.
      /me shrugs

  8. Re:Oracle was the first SQL relational database .. by Anonymous Coward · · Score: 4, Informative

    Relational databases and SQL was started with E.F. Codd at IBM. Follow the link for a little history that includes a story of the start of Ingres at Berkeley.

    http://www.nap.edu/readingroom/books/far/ch6.htm l

  9. Re:Oracle was the first SQL relational database .. by Anonymous Coward · · Score: 3, Informative

    Which is amazing, since IBM invented SQL for System R, which was first commercially installed at Pratt & Whitney in 1977. Soon after System R, IBM followed up with SQL/DS (for VM/CMS) and DB2 (for MVS).

  10. Ingres and Postgres by Anonymous Coward · · Score: 3, Informative

    I believe that Ingres was the predecessor of Postgres. I believe that both of them came out of Michael Stonebreaker. Ingres was it's own company until CA bought it in the early or mid 1990s. Postgres also became a product (UniSQL? Is that right?)... but in the end that product failed.

    In fact, Ingres was once a major leader, but it kind of lost it's cookies thanks to Sybase, Oracle, and even Digital's RDB. And I don't think too many Ingres users were happy when CA bought it up.

    1. Re:Ingres and Postgres by Anonymous Coward · · Score: 1, Informative

      CA has marginalized the development Ingres for years now. The product has not progressed (in terms of features or fixes) in years. It is the has-been of all has-beens. Please won't you help CA out, oss community, since they are too goddamn cheap to hire the developers to properly support their DB?

    2. Re:Ingres and Postgres by Anonymous Coward · · Score: 1, Informative

      IIRC, Postgres saw a brief life as Illustra, which was acquired and borged into Informix as its O-R solution. While a good/interesting product, it was a commercial flop, as the major customers weren't ready for, or weren't interested in, O-R capabilities (which seems to be the case to this day). IFMX kinda bet the house on OR, which is (in part) why they got borged into IBM/DB2.

      Another IIRC, commercial Ingres suffered from a reliance on the original C code written in the late 70's by UCB grad students, and never got a significant rewrite, which is why the product began to suffer from code-rot a lot earlier than its contemporaries. While Postgres comes from the same lineage as Ingres, I believe Pg's source base took advantage of 10+ years of software engineering advancements, and has hence been a more robust product.

    3. Re:Ingres and Postgres by Anonymous Coward · · Score: 0

      Ingres was it's own company

      "its".
      No apostrophe.

    4. Re:Ingres and Postgres by __aapopf3474 · · Score: 1
      Yup, CA has been in the news in a not so nice way lately with the CEO Sanjay Kumar stepping down in the wake of a SEC probe:
      Kumar's resignation may help the company reach a settlement with the U.S. Justice Department and the Securities and Exchange Commission, which began a formal probe into the company's accounting in May 2002. Chief Financial Officer Ira Zar said "high-level'' executives were involved in hiding revenue drops when he pleaded guilty to securities fraud earlier this month.
      The funny thing is that Kumar's predecessor, Charles Wang, had similar bad press in 1998 when it came to light that top executives got $1.1 billion in stock when the stock stayed above a certain level for a certain amount of time.

      However, the expenses of the stock plan were never booked. When all this came out, the stock price dropped 31% the next day.

      See: Graef Crystal's 4/21/04 column on Bloomberg

    5. Re:Ingres and Postgres by brre · · Score: 2, Informative
      Basically correct.

      University INGRES was Stonebraker's RDMBS designed and implemented at UCB. He founded a company Ingres to bring it to market. Ingres developed INGRES for over 10 years into an industrial strength database system, adding query and application development tools, forms tools, reporting tools, DBA tools, programming language integration, application generation, porting to all major UNIX systems as well as VMS and MS-DOS, re-architected it to a client-server model, added support for more storage structures, a state-of-the-art query optimizer, large objects, user-defined datatypes, transactions, database procedures, database rules, SQL support, client-server architecture, multi-threaded high performance database engine, network and distributed databases, gateways to legacy databases, and a GUI environment for developing GUI database applications.

      So it's not accurate to say that SQL, or any of the features mentioned above, were added by CA.

      Ingres the company became RTI became ASK. Later ASK was acquired by Computer Associates.

      Next month will mark10th anniversary of the takeover of Ingres.

    6. Re:Ingres and Postgres by hey+hey+hey · · Score: 1
      never got a significant rewrite

      Snicker. Do you really think they hired all those programmers, and never, in all those years, did a rewrite of the core system? They weren't idiots...

    7. Re:Ingres and Postgres by Anonymous Coward · · Score: 0

      Ingres 6.0 was a re-write. With some painful new bugs.

      Try wasting days figuring out the bug in their new feature stored procedures - limited ot about 60 lines of code or less ...

      6.1 fixed a lot of issues

      6.3 really rocked for it's time. We supported 350+ users on a Sparc pizza box back end for major brokerage company. No crashes, no contsant patching like Oracle.

      If the current version is only as good as 6.3 then it's still years ahead of PostGres or MySQL.

    8. Re:Ingres and Postgres by spacefrog · · Score: 3, Interesting

      I don't think too many Ingres users were happy when CA bought it up.

      No user of a package is happy when CA buys it up. In the early 90's they went on a buying spree, buying up some things that were popular and useful (e.g. Clipper), some things that were mediocre but could have been made into players (e.g. Realizer) and some were absolute crap that they managed to revise to crappier (DBFast, and some weird French-made Windows word processor).

      Some of those products were failures before CA gave them the kiss of death. The ones that weren't, CA managed to destroy all value of on their own.

      CA is the kiss of death. If CA buys one of your software vendors, start shopping for a replacement now.

      Former Clipper developer, but I'm not bitter or anything. Noooo, of course not.

    9. Re:Ingres and Postgres by sapbasisnerd · · Score: 1
      Ingres the company became RTI became ASK. Later ASK was acquired by Computer Associates. I think the actual timeline was:

      Relational Technologies Inc. became RTI became Ingres. Later ASK bought Ingres, even later CA bought ASK.

    10. Re:Ingres and Postgres by johnnyb · · Score: 1

      "However, the expenses of the stock plan were never booked."

      If they were stock options, that would actually be pretty normal. For some reason it has taken decades to convince wall street that options really were an expense. Warren Buffet gave an excellent piece on this in one of his letters to shareholders, but I can't find the link.

    11. Re:Ingres and Postgres by wib · · Score: 2, Informative

      I am not quite sure this is correct. There have been sucessive new releases of the product since 1994 when CA acquired ASK (6 major releases). CA were in closed beta with the next release until the announcment yesterday.

      Would you call Cluster support, replication, parallel query execution, numerous performance enhancements amongst others, not progressing the product. The company still has development and support staff located in every continent.

      I still remember what Ingres was like after CA acquired it from ASK. The OpenIngres 1.0 release was canned due to the marginalized development by ASK. it took 2 major releases before stability returned. Many ex-Ingres staff still lament about how good it was under ASK. Perhaps if ASK had spent its money on development rather than the parties perhaps Ingres would be in better state after the ASK acquisition.

  11. Another has-been set free by k4_pacific · · Score: 4, Insightful

    It seems like this sort of announcement is becoming a common thing. Heck, even Microsoft did this with their WIX installer.

    Step 1: Dust off the source code for something that hasn't made any money in years.

    Step 2: Slap a GPL on it.

    Step 3: Release it to SourceForge.

    Step 3: Gain the goodwill of the open-source community.

    --
    Unknown host pong.
    1. Re:Another has-been set free by polin8 · · Score: 1

      no, never a GPL an OSI approved "safe" license.

    2. Re:Another has-been set free by Trailer+Trash · · Score: 4, Insightful

      Bring it on! Seriously, if something isn't making money for a company, what's to lose? The more source we have available, the better off the entire computing industry is...

    3. Re:Another has-been set free by Linus+Sixpack · · Score: 4, Insightful

      Yea but available code without a simple free license is a problem as well as a bonus.

      At least it will make patent searches easier :)

      ls

    4. Re:Another has-been set free by cookd · · Score: 1

      WiX is most definitely not dusty -- it is still under active development. It never made money because it was internal-only until now. A lot of teams at Microsoft use it for the stuff they ship.

      --
      Time flies like an arrow. Fruit flies like a banana.
    5. Re:Another has-been set free by Kardamon · · Score: 1

      I agree. In fact I would like CA to open source "Intelligent Warehouse". IW was an HP middleware product for internal use which was later marketed by Platinum. CA bought Platinum, and IW(latest version: 3.4.5) was taken out of support on May 1st, 2003. I'm now working for a client who still uses it and it still is a very good product. Is anybody at CA reading this??

      --
      -- Qu'est-ce que la propriété intellectuelle? It is thought control.
  12. Ah, this brings back memories.... by hendersj · · Score: 5, Interesting

    When I was in college back in 89-93, we replaced an aging IBM mainframe with some brand new Sun equipment; one of the classes was a database class, and after the 4361 was retired, we put Ingres on SunOS 4.2 for that class.

    The thing kept falling over when the CS students would try to work with it - in any given time period, if there were more than 2 or 3 students using it, it would just shrivel up and die.

    It was so notorious for this that when we obtained source code to DikuMUD and implemented our own MUD server, we created a character called "Ingres". If you attacked it with any of the vast array of weaponry available, you could never cause any damage. It would never damage back (as it was harmless), but there was one way to kill it:

    LOOK AT INGRES

    Ah, the memories....

    --
    Insanity is a gradual process; don't rush it.
  13. Re:Oracle was the first SQL relational database .. by sapbasisnerd · · Score: 5, Informative
    RTFA, it says Ingres was the first [non-SQL] relational database, and that SQL was added later. Ingres used a Query language called QUEL.

    Now it says that CA added SQL which if I'm remembering isn't true, SQL was in the product well before CA bought it.

    Ingres was made by Relational Technology Inc. (at one point in the early eighties there were three database companies that had names containing "relational" and they all eventually changed their names to that of their product (Ingres, Oracle and Informix).

    I wrote an application in PC-Ingres in 1986 that used QUEL, I stopped paying attention shortly after that as I went to work for Oracle. Then in 1991 when I left Oracle to go to DEC Ingres was on my radar again as we resold it as "ULTRIX-SQL" and obviously by that point it had gained SQL capabilities. Sometime after that Ingres was in financial trouble and got bought by ASK because they had an application that was based on Ingres and felt they couldn't afford to have them go out of business. Later CA bought ASK.

  14. Actually by Anonymous Coward · · Score: 0

    CA has been busy embedding Ingres into almost every single one of their products that requires any sort of data store for quite some time. I read last year (sorry, no links) that Ingres is ironically one of the fastest growing databases around, because every time you install any CA product, you're installing Ingres (whether you know it or not).

  15. Until ... by A+nonymous+Coward · · Score: 4, Insightful

    Until you try an outer join or something other than trivial SELECTs. At least some of them have different syntax from others, and then there's the matter of working around MySQL's inadequacies. DBI is of very little help.

  16. Re:JOIN THE REVOLUTION by Anonymous Coward · · Score: 0
    find out how YOU can make a difference!!!!

    Let me guess: Lots of useless whining and trolling? Why don't you go outside for a change?

  17. And Groklaw is being an ungrateful @$$ about it by Anonymous Coward · · Score: 0

    They're getting too damn big for their britches over there if you ask me.

    1. Re:And Groklaw is being an ungrateful @$$ about it by hendersj · · Score: 1

      Well, I think it's quite prudent to consider carefully the history of the company in question - they have a very long and varied history of acquisitions and how they have dealt with those aquired companies over the years has been....shall we say "interesting"?

      Given that they have rather suddenly 'seen the light' for open source, it's only prudent to be cautious, especially given their other corporate relationships.

      So there you have it....I didn't ask you, and you didn't ask me. So we're even.

      --
      Insanity is a gradual process; don't rush it.
  18. Re:Oracle was the first - WRONG by neongenesis · · Score: 2, Interesting


    The Multics Relational Data Store (MRDS, The French loved the name) was the first commercial database system, marketed by Honeywell on the Multics in 1977. It had an early SQL as the standards bodies churned the standard into shape.


    I know, Oracle was early, but as in so many other things, Multics was first.

  19. First real relational database by Openstandards.net · · Score: 1, Interesting
    The first real relational database, to my knowledge, was Ashton Tate's dBase II, which I used on CP/M in the early 80s before DOS even existed.

    If I remember, I think dBase I, which was never on the market, was created by Bell Labs. Bell Labs later sued Ashton Tate for using some code from dBase I, and won. Borland then bought dBase when III Plus was out, IIRC.

    1. Re:First real relational database by brank · · Score: 4, Informative

      Edgar F. Codd came up with the "relational model" while working at IBM San Jose after becoming dissatisfied with every other DB ever written.

      Codd immediately became mired in internal politics (one of the DBs Codd was dissatisfied with was IBM's own :). But an IBM research group at San Jose created System R anyway,. That was the first relational database in the early 70's. Ingres came almost right after, when some Berkley scientists decided it might be fun to play with the ideas that were slowly filtering out of IBM.

      dBase came out of a JPL (Jeb Long) engineer's work, and the first versions did owe a lot to earlier mainframe DBs. The first relational DB for home computers, maybe, but not the first relational database.

      --
      it's green.
    2. Re:First real relational database by Doctor+Faustus · · Score: 1

      "dBase II" was the name of Wayne Ratliff's "Vulcan" after Ashton-Tate bought it (changing their own name in the process, I believe from "Discount Software"). It may have been the first microcomputer relational database, but a bunch of other comments here are saying that Ingres also originated in 1978.

      If you don't restrict yourself to commercial systems, a quick Google search brings up articles on IBM's experimental "System R" as early as 1973.

    3. Re:First real relational database by darnok · · Score: 2, Insightful

      If you're prepared to accept dBase II as a relational database, then I'd submit that IBM's ISAM/VSAM files have been around a good deal longer than that and they're fairly similar in terms of capability. No transaction level support, no ACID compliance, etc.

      In terms of longevity, I've heard that William the Conqueror was tracking his troops using ISAM files when he invaded England in 1066.

    4. Re:First real relational database by Nutria · · Score: 0
      first microcomputer relational database,

      Gah!! dBaseX is about as far from being a relational DBMS as possible. In fast, it's not a DBM*S* at all: the programmer has to do everything except manage the indexes.

      R:Base was the first uP RDBMS.

      --
      "I don't know, therefore Aliens" Wafflebox1
    5. Re:First real relational database by Openstandards.net · · Score: 1
      Did IBM's ISAM/VSAM database permit you to declaratively join tables via keys and enforce unique constraints on groups of colums to create keys? This is what defined a database as relational.

      Transactional concepts are abstracted so that

      • They are not required to relate data.
      • A database that supports ACID transactions does not have to be relational.
      They are completely independent database concepts.
    6. Re:First real relational database by Anonymous Coward · · Score: 0

      I concur. If dBase II can be said to be relational, then any data persistence mechanism is too. Some other candidates beyond ISAM (non-exhaustive list):

      http://www.amherst.edu/~ermace/sth/photos.html
      http://www.mkzdk.org/carnac/guiden.html
      http://www.memphis.edu/egypt/giza.htm
      http://www.crystalinks.com/chinawall.html
      http://archaeology.la.asu.edu/teo/intro/sun.htm

    7. Re:First real relational database by hughk · · Score: 1

      Behind one major system for trading financial securities (the largest for derivatives, at least) is a straightforward ISAM-type mechanism. Relational was too slow. The ISAM files certainly qualify for being called a database and the flavour of ISAM they use has ACID as well. However there are no constratints, no referential integrity and no space management. In short, there is a non-relational database without a management system.

      --
      See my journal, I write things there
    8. Re:First real relational database by StormReaver · · Score: 1

      "In terms of longevity, I've heard that William the Conqueror was tracking his troops using ISAM files when he invaded England in 1066."

      England? That's in Texas, right? ;)

    9. Re:First real relational database by Anonymous Coward · · Score: 0
      If I remember, I think dBase I, which was never on the market, was created by Bell Labs.

      That didn't sound right so I looked around and found this:

      1981 November: Ashton-Tate repackaged Wayne Ratliff's Vulcan database program as dBase II, bringing relational database technology to the PC. There was never a dBase I, nor an Ashton, nor a Tate, (though a parrot was later named Ashton) bringing deceptive product naming to the PC. Ed Esber brought real MBA style business management to the company, destroying it completely. The parrot died and Ashton-Tate was sold to Borland, where dBase died.

      The version "II" was pure marketing. Yes, even in 1981 people were afraid of "version 1" of anything.



      http://www.aaxnet.com/info/hist.html

      -rick
  20. Re:Oracle was the first SQL relational database .. by Tablizer · · Score: 2, Informative

    Some background info on QUEL if anyone is interested.

  21. The Greatest Upgrade to Ingres... by 10scjed · · Score: 4, Informative

    Is removing that god-awful CA licensing, anyone who has deployed CA products knows what I mean. That RegisterIT/LicenseIT OLF garbage, even with a "valid" license file it would time out half the time. And forget about changing hardware or a NIC, they bind their license files to your machines MAC address. CA Licensing is worse than Microsoft's activation.

    --
    --10scjed IANAL,AFAIK
    1. Re:The Greatest Upgrade to Ingres... by Anonymous Coward · · Score: 0

      As a former Ingres DBA, I can only say "Mod that comment up".

      Amazing they're going from one of the most extreme & stupid licensing schemes ever to have crawled out of the stinking ooze of the corporate world to an open source license!

      When it first came out, their crazy license scheme assumed you were using microsoft NT. They couldn't imagine that a Unix shop running a Unix dbms didn't use NT!

    2. Re:The Greatest Upgrade to Ingres... by HiThere · · Score: 1

      Welll... nobody seems to have seen the license that they intend to be using. They are reported as saying that it's an open source license, but it's a brand new one, and not on any approved list of licenses. So it may be good, or it may not. We'll need to wait until we've seen it.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  22. What about more interesting parts - bad PR & by Anonymous Coward · · Score: 0

    What about that this is as diversion from the accounting scandal?

    What about the bigger impact of KGEM helping with making Level B1 easier?

    KGEM, etc

  23. Please learn how to make links. by Anonymous Coward · · Score: 1, Informative
    Please learn how to make links.
    <a href="http://www.nap.edu/readingroom/books/far/ch6 .html">the story</a>
    yields: the story
  24. Replication? by Anonymous Coward · · Score: 0

    Sorry, I don't know much about this database. However, if it has replication, could that feature be ported to PostgreSQL? Which needs replication... like now. And yes, I know of the commercial replication add-ons, but an official one would be nice.

  25. Re:Oracle was the first SQL relational database .. by fmorgan · · Score: 1

    The CIA (and the Navy) bought Oracle V1 and V2, not really to use it - who could use it at the time, but as a kind of "federal funding" to help promising technology (kind of VC fund).
    I think Oracle3 was rewritten to be in C (and as such, portable) and it was kind of somewhat usable; V4 was usable and I actually deployed it in production!

  26. Illustra was also in the Ingres Postgres bloodline by uiil · · Score: 1

    Stonebreaker also created the Illustra object relational database after leaving academia.

    It seemed to have been created with the intention of having the big players buy it out, just to eliminate it as a competitor.

    Informix bought them, then IBM bought Informix.

    The only Illustra bit that seems to have survived was the "datablade" terminology for sets of structures and functions for specific data types.

    Some of the original Illustra datablades were fun to fiddle with, a long time ago...

  27. although it was the first commercial SQL database by Anonymous Coward · · Score: 1, Informative

    Much of the actual research (and the SeQueL language itself) was done by IBM. Hell, Codd worked for them.

    Also, so the story (told by current and former IBMers I've met) is that Oracle's query optimizer was one of the discarded (open) research ones that IBM passed up for the one that formed the basis for what's DB2. Take that with a grain of salt.

  28. Re:Oracle was the first SQL relational database .. by kfg · · Score: 5, Informative

    Ingres was made by Relational Technology Inc

    Actually, it began it's life circa 1974 as a research project at UCB and was originally released with source under a BSD license.

    The more things change, the more they remain the same I guess.

    KFG

  29. Tools? by countach · · Score: 1

    Is this the same as the last commercial Ingres product? I wonder if this includes all the tools that Ingres had. Like report generators and application generators. Would be cool I guess if it has all that.

  30. CA CEO steps down in financial scandal by Anonymous Coward · · Score: 0

    I wonder if this has anything to do with their desperate effort to get on the OSS community's good side?

    http://www.computerworld.com/managementtopics/ma na gement/story/0,10801,92550,00.html?from=story_pick s

    CA is made up of dozens (hundreds?) of companies they've bought out, whose employees they've laid off and whose products they try and fail to integrate into a cohesive whole. I'm amazed they've stayed in business this long...

  31. License is *NOT* changing by HammerToe · · Score: 5, Informative

    Joel Burton best sums it up on ZopeZen:

    "eweek.com reported on the Plone Foundation and CA's involvement, but their information about Plone moving away from the GPL is not correct. This has not happened. For our FAQs on the foundation, please see http://plone.org/foundation/faq.

    I'm sitting here with Alan, Paul, and Mark Murphy, and we really want to make sure that every knows that this is a real mistake and we're trying to reach eweek to let them know to issue a retraction. We want to make certain that everyone understands that no changes have been made and that a change like this would never happen with discussion with the community as a whole. The Foundation is an exciting change for our community, and we don't want this mistaken information to let people lose site of that."

    1. Re:License is *NOT* changing by marko123 · · Score: 1

      We want to make certain that everyone understands that no changes have been made and that a change like this would never happen with discussion with the community as a whole

      heh, whoops?

      Anyway guys, good luck at re-educating the great unwashed :)

      --
      http://pcblues.com - Digits and Wood
  32. Here you go by Chuck+Chunder · · Score: 2, Funny
    10 PRINT "HELLO!"
    20 GOTO 10
    You don't need to thank me, I'm more than happy to do my part for the betterment of the entire computing industry.
    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
    1. Re:Here you go by _Sprocket_ · · Score: 2, Funny

      You might want to check on who owns that before you give it away. Seems like I've seen it elsewhere. Granted, it could be public domain. But it could also belong to SCO.

  33. PostgreSQL is Ingres successor by Anonymous Coward · · Score: 0

    Check it yourself . I wonder why would anybody want to use Ingres, when PostgreSQL is so much better.

  34. Bush for President in 2004 -- of Iraq. by Anonymous Coward · · Score: 0

    "Bush for ex-President 2004"

    Bush for President -- of Iraq. He made the mess, let him fix it.

    He lied, they died.

  35. Re:Oracle was the first SQL relational database .. by hey+hey+hey · · Score: 1

    Originally, the University (or at least the Ingres Project) tried to sell it. They got into a bunch of trouble with AT&T over it (as UC only had an educational license, not a commercial license).

  36. Re:Oracle was the first SQL relational database .. by hughk · · Score: 1
    Ultrix-SQL??

    I thought DEC had their own RDMS, RDB which also ran on Ultrix. In the early days at least, RDB shared its backend with DEC's CODASYL (Hierarchical) DBMS, DBM-32, but it certainly qualified as relational.

    --
    See my journal, I write things there
  37. Re:WHO CARES!!! by Anonymous Coward · · Score: 0

    Yea he is

  38. As someone who uses Ingres... by jregel · · Score: 4, Informative

    I work for a company that runs it's entire product base on Ingres II (2.0) and we're in the process of migrating to Advantage Ingres 2.6 (and also building a Linux version). I've also have some experience in MySQL so have a basis for comparison.

    While MySQL is fine for non-critical apps, and is especially easy to use for web applications, Ingres is designed to manage large databases. We have several of the largest local authorities in the UK running Ingres on big Sun boxes (E10K / E15K) with databases in the 10s of GBs. Ingres can handle this fine. There are some things that Oracle can do that Ingres still can't, but the ease of administering an Ingres installation is trivial. I've sat down with Oracle DBAs and they have been astounded at how easy it is to create new databases, take backups etc.

    The biggest weakness with Ingres has always been the lack of users (and hence a limited community). It's everywhere because most CA products that require a DB have Ingres running underneath (such as Brightstor Enterprise backup), but most people don't get to see it. Open Sourcing Ingres is very good for us, and excellent for the OSS community as it gives us a powerful, enterprise-grade DBMS server.

    This is very exciting news, and DBA-gurus would be wise to check this out. W00t.

  39. IIRC MS SQLServer was originally a fork of Ingress by Dr.Knackerator · · Score: 0

    Yep i think MS bought it a long time ago and SQLServer 1 was basically all Ingress plus some extras. Im trying to rememeber whether it *was* Ingres, MS did buy in a product it wasn't developed from scratch in house.

  40. Re:IIRC MS SQLServer was originally a fork of Ingr by mccalli · · Score: 1
    Im trying to rememeber whether it *was* Ingres, MS did buy in a product it wasn't developed from scratch in house.

    Sybase.

    Cheers,
    Ian

  41. Re:IIRC MS SQLServer was originally a fork of Ingr by Dr.Knackerator · · Score: 1

    heh yeah that's right. There are so many dead databases its hard to keep up :)

  42. BZZZT! Wrong! by Anonymous Coward · · Score: 0

    Step 2: Slap a GPL on it.
    It's not GPL. It's some other license that nobody seems to have found a link to. Almost for sure, it will some crap license that either does not give, or does not preserve, the freedoms that the GPL gives and preserves.

  43. As an Oracle DBA by Moderation+abuser · · Score: 3, Informative

    I'll second your motion. Almost any RDBMS is simpler to manage than Oracle is. I've used Oracle, Informix, Postgresql, MS SQL server, mysql, etc etc, though not Ingres.

    I honestly don't see the attraction Oracle has to companies. 99% of corporate databases are trivial, they could be implemented on text files or the dreaded spreadsheet and make no use at all of the features Oracle has. It's just that 1% which need Oracle and associated DBAs so why insist on Oracle for everything? It's wildly expensive.

    --
    Government of the people, by corporate executives, for corporate profits.
    1. Re:As an Oracle DBA by Anonymous Coward · · Score: 0

      The pay rates are also correspondingly higher. I'd recommend Oracle over Ingres any day (not technically, but it's worth another 15 quid an hour to me)

    2. Re:As an Oracle DBA by mangu · · Score: 2, Insightful
      I agree completely about Oracle being a bitch to manage and vastly overpowered for almost all databases. I have been using Postgres for all new applications I create, and Ingres and Oracle for legacy applications. I believe the reason why so many developers choose Oracle is twofold: first, it's so widely used, many people are familiar with it. Second, nobody ever got fired for choosing Oracle. People feel confident that no matter what database they throw at Oracle, it will be able to handle it.


      As for the cost, well, they include it in the business plan. Except for very small companies, Oracle is considered "affordable" by the upper management.

    3. Re:As an Oracle DBA by leandrod · · Score: 1
      > Almost any RDBMS is simpler to manage than Oracle is

      Except that there aren't many left, only the QUEL portion of Ingres and Alphora Dataphor. All the rest are SQL.

      > I honestly don't see the attraction Oracle has to companies

      Proprietary lock-in and herd behaviour.

      --
      Leandro Guimarães Faria Corcete DUTRA
      DA, DBA, SysAdmin, Data Modeller
      GNU Project, Debian GNU/Lin
    4. Re:As an Oracle DBA by Moderation+abuser · · Score: 1

      True.

      --
      Government of the people, by corporate executives, for corporate profits.
    5. Re:As an Oracle DBA by Herbmaster · · Score: 1

      Almost any RDBMS is simpler to manage than Oracle is. I've used Oracle, Informix, Postgresql, MS SQL server, mysql, etc etc, though not Ingres.

      You didn't mention DB2. If you had, it would be in the "worse than Oracle" category, I assure you (I've managed DB2 on windows, unix, and - ugh - 390).

      --
      I'm not a smorgasbord.
  44. Re:Oracle was the first SQL relational database .. by Anonymous Coward · · Score: 3, Informative

    The ingres project was started around the same time as the unichs/unix project. I believe the first commercial unix system outside of Bell labs was for Stonebraker's ingres project.

    At that stage it used QUEL, which was widely regarded as superior to SQL - IBM's query language. Have a read of CJ Date's book for a comparison. It lost out YAVBT (Yet Another Vhs-Betamax Thing).

    SQL, rules, triggers, procedures etc added in late 80's, so by 1991 release 6.0 was technically the top relational db. The query optimizer was without doubt the best. Superior marketing and rapidly improving technology gave Oracle a huge market advantage by the mid 90's. At the same time Ingres stagnated as the buggy OpenIngres version was rolled out.

    CA bought ingres in the mid 90's. After a period of disorganisation while most of the original Californian development team were laid off or quit, CA began to add new features again & the product became a lot more solid.

    It is currently used by legacy sites & as a backend for CA's products. If you buy something like Unicentre, you'll get Ingres quietly installed as well.

    Technically:
    - behind Oracle/DB2, but evolving at higher speed.
    - ahead of PostGRES & mysql is still a joke.
    - only real advantage over Oracle since the early 90's is it's ease of database administration. It pretty much manages itself, which is why it's niche is now as a backend to other products.

  45. Re:IIRC MS SQLServer was originally a fork of Ingr by supersnail · · Score: 1


    I thought MS SQLServer was origonally SYBASE.

    MS forked off at about SYSBASE v6.

    --
    Old COBOL programmers never die. They just code in C.
  46. Links in /. are a PITA by Anonymous Coward · · Score: 1, Interesting

    Link are a pain in the ass in slashdot because you have to remember the actual HTML tags. Stupid.

    A lot of other sites allow you to create it down below the text area (sort of an "html helper" area).

    Some of us have people who work for us who do the HTML tags. Some of us haven't done an HTML tag since '96. I realize you were just finishing up the 4th grade at that point, but really, some of us have been around the block a few times.

    1. Re:Links in /. are a PITA by Anonymous Coward · · Score: 0

      If you've been around the block a few times and you can't remember how to make a link, maybe you need to find a new block. It's one thing to not understand all the nuances of frames or forms. A simple link, however, is within the capability of a third grader.

    2. Re:Links in /. are a PITA by BarryNorton · · Score: 1

      Yeah, I'm sorry but it's the very essence of HTML - if you've forgotten that, riding a bicycle must be hard for you these days!

    3. Re:Links in /. are a PITA by NateTech · · Score: 1

      Some of us have people who do the HTML tags for us? Gone soft over the years and can't cut it anymore, eh?

      The whole point is that it's the SAME HTML tag you used in '96. Only a moron would forget it... the syntax is quite simple and you can steal it from every single web page you've ever looked at ever by just clicking on "View Source", you moron.

      As someone else who's "been around the block" I don't find it particularly difficult to remember the same tag I've been using to create hyperlinks in HTML for about a decade now.

      You think there might be some HTML references on the WEB???? Whoa!!! Really?!?!

      You're a shining star of laziness. At least I'll tip my hat to you there... keep slouchin', Mr. Around the Block! You lazy AC SOB you!

      --
      +++OK ATH
  47. Because by Anonymous Coward · · Score: 0

    "but my clients don't seem to care as long as their sites are running. "

    Spoken like a kid who doesn't have to clean up after his own mess.

    No, seriously, the reason it works for you is because you build trivial sites. Those of us who actually make money at e-commerce can afford to do it the right way, and not pay some lone hacker to build a site, no matter how "good" he thinks he is.

  48. When CA buys a product it is EOL by Anonymous Coward · · Score: 0

    That's not a flame, that's CA's business model.

    As a manager at a company, you have to realize that when CA buys a product you depend on, its time to budget to replace that product in the next 12-24 months.

    Again, not a flame, just a statement of realism.

  49. Tools for the job by 16K+Ram+Pack · · Score: 2, Insightful
    I get a bit fed up with all the PHP/VB bashing as well.

    A LOT of companies use these tools, partly because they are simple and quick.

    I've also used MS Access when it suited. For getting something implemented in a department in a very short deadline as an interim solution to something more scalable and stable.

    1. Re:Tools for the job by Tukla · · Score: 1

      The problem, of course, is how often that "interim" solution becomes the "final" solution. I had to nursemaid one of my own "interim" solutions twice a week for nearly seven years because it worked "well enough"...from the customer's point of view. They didn't know that I was physically taking their data home with me to upload it and download results from my own PC because my "interim" solution stopped functioning at work after we were upgraded to WinNT.

  50. Re:IIRC MS SQLServer was originally a fork of Ingr by vidarh · · Score: 1

    Uhm.. I think Sybase would object to on of their flahship products being called "dead database".

  51. Post/Ing/Whatever -gres needs marketing by Qbertino · · Score: 2, Interesting

    Postgres is one of those products that are cool but don't soar due to a hazy unhip image. People either use MySQL (most know DB) or something like SAP(!!)DB or it's follow-up MaxDB.
    For one I'd say Postgres (or is it PostgreSQL???) could _really_ use a better, grittier name. And the Site needs an optical redo.
    My 2 cents.

    --
    We suffer more in our imagination than in reality. - Seneca
  52. Ingres? by Colonel+Cholling · · Score: 1

    Is that like when the Japanese do a bad translation from Spanish into English?

    --

    I am Sartre of the Borg. Existence is futile.
  53. CA denied this last year by Anonymous Coward · · Score: 0

    Interesting debate on this very subject in the Ingres newsgroup a year ago. It prompted a denial that Ingres would ever go open source. Looks like they had another think...

  54. Re:Oracle was the first SQL relational database .. by sapbasisnerd · · Score: 1

    RDB was SQL but it ran only of VMS for a very long time, I don't recall that it ever ran on Ultrix. DEC bundled a runtime license for Ingres (called Ultrix-SQL) with some versions of Ultrix and it was bundled into some of the Ultrix versions of some of the Polycenter products.

  55. History of ingres / postgresql by jlrobins_uncc · · Score: 1

    From the good book

    1. Re:History of ingres / postgresql by Anonymous Coward · · Score: 0

      That site doesn't tell the whole story. The commercialization of Ingres was by Relational Technology Inc. which was later renamed Ingres Corporation. Shrtly thereafter it was purchased by ASK Computer Systems which was purchased by CA in June, 1994 as ASK was in a cash-starved death spiral.

      The most interesting part of the CA takeover was that they tried to force the engineers to sign noncompete agreements to keep their jobs and a few hundred of them got up and walked out. This suprised CA as it had never happened before. Perhaps someone else would care to comment...

  56. Re:IIRC MS SQLServer was originally a fork of Ingr by Anonymous Coward · · Score: 0

    Actually they purchased the rights to use the Sybase 4.9.2 source code. I don't remember if there was a Sybase 6 but I do know that they jumped several numbers to "System 10".

  57. Re:IIRC MS SQLServer was originally a fork of Ingr by Some+Pig! · · Score: 1

    Uhm.. I think Sybase would object to on of their flahship products being called "dead database".

    May I add, ASE 12.5 rocks my world.
  58. Re:Oracle was the first SQL relational database .. by leandrod · · Score: 0
    > IBM invented SQL for System R

    Let's get that straight. System R was not an invention, but a misdevelopment from Codd's work on the Relational Model. SQL is bad.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  59. Re:Oracle was the first SQL relational database .. by hughk · · Score: 1

    RDB definitely ran on Ultrix later (or maybe by then it was OSF/1). I agree that porting would have been an 'interesting problem' due to an innate awareness of the VMS lock manager. Very nice, but not very portable.

    --
    See my journal, I write things there
  60. Re:Oracle was the first SQL relational database .. by leandrod · · Score: 1
    > System R, which was first commercially installed at Pratt & Whitney in 1977

    I'd love to see this straightened out, but I know for sure that the first deployments of System R weren't General Availability, more like beta testing.

    So the argument goes that Oracle was released before SQL/DS reached GA, which is the IBM equivalent of a release.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  61. Re:Oracle was the first SQL relational database .. by sapbasisnerd · · Score: 1
    definitely ran on Ultrix later (or maybe by then it was OSF/1)

    Keep in mind that Ultrix and OSF/1 (later Digital UNIX) were completely separate UNIX implementations.

    OSF/1 was a new UNIX implementation that was released ONLY on Alpha machines (or rather, the Digital version of OSF/1 was only released on Alpha, the IBM and HP versions of OSF/1 were respecively called AIX and HP/UX but I digress).

    Ultrix ran on VAXen and on the MIPS chip DECstation/DECserver machines (it also was beta tested but never shipped on PDP-11, I know I was a beta tester).

    I still recall that RDB for UNIX was not publically released on Ultrix but I may be wrong, by the time it was starting to hit the streets I wasn't paying attention to databases that didn't run under SAP, including Ingres, Sybase and RDB.

  62. Re:Oracle was the first - WRONG by leandrod · · Score: 1
    > The Multics Relational Data Store (MRDS [...] ) was the first commercial database system

    It wasn't, there were DBMSs such as CA IDMS and IBM IMS much before SQL came to light.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  63. Re:although it was the first commercial SQL databa by leandrod · · Score: 2
    > Oracle's query optimizer was one of the discarded (open) research ones that IBM passed up for the one that formed the basis for what's DB2

    Indeed until v7 Oracle only had (or recommended) a rules-based optimiser vs IBM's cost-based one. This was one more proprietary lock-in for Oracle, since Oracle SQL coding was badly distorted to extract the last grain of performance, making it slow in better optimisers.

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin
  64. Re:Oracle was the first SQL relational database .. by hughk · · Score: 1
    It would not be totally correct to say they were completely different. The kernel definitely was though. AIX was nothing to do with OSF/1 and couldn't pass half the validation suites even now, same for HP/UX. OSF/1 effectively being a standard of its own became useless (a bit like DECnet-OSI).

    I don't know about a full release of RDB for Ultrix, but I definitely remember an SPD for RDB/Ultrix-32.

    --
    See my journal, I write things there
  65. Re:Oracle was the first SQL relational database .. by Anonymous Coward · · Score: 0

    1. SQL was an IBM development. It was a play on the language name of "Quel".
    2. SQL is bad.
    3. Codd's relational database work was an IBM project. Codd was an IBM employee.
    4. System R was an IBM development. SQL/DS was based on the System R codebase.
    5. System R was used in customer's production systems, under VM/CMS, starting in 1977.
    6. SQL is the now the defacto relational database language.

    Hope that helps!

    Hope that helps you understand the big picture

  66. Re:Oracle was the first SQL relational database .. by hey+hey+hey · · Score: 1
    I believe the first commercial unix system outside of Bell labs was for Stonebraker's ingres project.

    Commercial UNIX predates Mike starting the Ingres project. More to the point, as a University, CAL didn't have a commercial license, just an educational one.

  67. Stored Procedures by Anonymous Coward · · Score: 0

    Try using stored procedures instead of inline SQL. Better encapsulation, exception handling, easier to develop (separate database development and query optimization from application construction...) etc.

  68. Un-GPL-ification. by ninejaguar · · Score: 1
    Apparently, Plone was already GPL'd. Computer Assoc, a seedy bunch to begin with, will remove Plone from under the GPL and put it under a weaker license.

    If there's enough momentum (if the app is any good) you should see a fork that will continue development under the GPL.

    = 9J =

  69. Re:Oracle was the first SQL relational database .. by NateTech · · Score: 1

    So you're saying that crap was released before some other really bad crap that eventually wasn't so bad, but still crap.

    Cool. Sounds just like today. Of course, we're up to Crap version 10 or 20 or something like that now.

    --
    +++OK ATH
  70. Re:Oracle was the first SQL relational database .. by leandrod · · Score: 1

    It couldn't be, since SQL ain't relational...

    --
    Leandro Guimarães Faria Corcete DUTRA
    DA, DBA, SysAdmin, Data Modeller
    GNU Project, Debian GNU/Lin