mSQL: It's Baaaccckkkkk 65
Leomania writes "In this press release on the mSQL (aka Mini SQL) website, it appears that mSQL is once again under development. A new release is slated for February 15th, and support will be available starting February 1st."
Why? (Score:1)
Re:Competition is not good in Open Source (Score:2)
Choice is good, and the competition between the different choices makes each contender better. I could go on about how much I disagree with your idea, but this hangover is killing me.
Re:why? (Score:2)
Re:Great just ordered $40 MySQL book (Score:1)
why not use postgresql now? it's had transactions for a couple years.
use LaTeX? want an online reference manager that
Re:by the same logic.. (Score:1)
I forgot to mention TUX and khttpd battling IIS (Score:2)
Differentiation and SQL Products (Score:1)
MySQL does a great job of doing things; yeah, it doesn't have transactions or foreign keys and the like to keep an incredible efficiency rate, but PostrgreSQL is another free alternative if you want to do this on the database end instead of in the program.
I'm not sure why, even if they completely GPL'ed mSQL, the world needs another SQL? Is there any mental differentiation between the products currently out there?
I think the problem here is simply mindshare and coming into a crowded SQL market where enterprise has already been adopting free alternatives to Oracle and the other extremely expensive SQL databases. Reinventing the wheel by introducing mSQL again seems futile at best, foolish at worse when they could be marketing their database expertise toward the fairly lucrative services industry for the enterprise sector.
--
Re:wahooO! (Score:1)
Re: (Score:1)
Re:Why both are far behind the competition. (Score:1)
PG has some features that IB does not have like user defined operators! and loadable SP and trigger languages. It does not have domains but it does have user defined datatypes.
The query optimizer is pretty nice (IB gets confused sometimes) and the import export facility is way better then IB.
It does not run on windoes tho. It has it's annoyances too (no outer joins yet but coming soon) but all and all a very nice DB that is actually fun to work with.
Re:why? (Score:2)
ok, granted. sorry, i haven't looked at msql in a long while.
but, don't you think this lends even more weight to my question? who's going to use msql, when there are better, more established open-source (or free software, take your pick) sql backends already?
and my first post wasn't a troll, to whatever moron moderated it as one.
--
Re:Why both are far behind the competition. (Score:1)
PG is damn good, and pretty quick besides. Good FK implementation with ON DELETE functionality built in. It has support for procedural language, but not quite as intuitive as Oracle's PL. My main gripe with it is the lack of a good context search. That's where Oracle really blows PG away, although there's no question that PG's physical DB structure is not as stable as Oracle's (if you can get it to run).
-Scott Miller
Re:wahooO! (Score:2)
Re:Competition is not good in Open Source (Score:3)
Competition is nice, but the most important thing is not competition, but having a choice.
Nothing would make me happier if, instead of halving a choice between half a dozen different poorly implemented solutions, there was just one excellent solution.
But the problem isn't that there are half a dozen different solution in your example, it's that they're all poor. It's not always the case that multiplicity correlates with quality.
The best open source projects have a monopoly, and suck all the development effort for that field - The Kernel and Apache for example.
So, by your definition, nobody is working on BSD. The researchers who come up with new networking protocols traditionally prefer BSD. Do they not count? Do the BSD security nuts not count? The reason why there is a lot of effort in Linux and Apache is because they are very open-ended and have a wide scope for extensibility. Most of the developers are working on the extensible parts, not the core.
Why do we need several different versions of SQL to be on the go? It would be far better if there were just one, and the quality of the product would improve also.
That's the beauty of standards. There *is* only one SQL available. All the implementations of SQL have different redeeming factors. Do you need Oracle 8 just to power your weblog?
Re:Erk! (Score:1)
Not much point here (Score:1)
I've seen a project where that's the case. It involved a lot of simple SELECT statements.
But still, why? MySQL and PostgreSQL are MUCH more full featured. And they're 100% open source.
Hopefully they'll improve the msql mini-sql-monitor. It's by far the worst command line SQL monitor I've used!
Of course since it's not GPL'd, they can't link it to GNU readline for command-history recall. Big problem there...
Forget it, guys.... (Score:1)
-Moondog
Re:why? (Score:2)
Re:Erk! (Score:1)
Re:Linux? (Score:1)
Linus decided to create Linux because minix did not satisfy his needs. BSD for x86 (386BSD, not even speaking of FreeBSD) did not exist at that time. I am former user of 386BSD 0.1 and NetBSD up to 0.9. But when I discovered Linux, it was way ahead of NetBSD (speaking about kernels around 0.99.11 and SLS distribution): shared libraries, much better stability, and wider hardware support.
-Yenya
--
Re:Competition is not good in Open Source (Score:1)
mSQL is for people who want really simple, really fast DB access. Not even mySQL can compete on that level (they've sacrificied some speed for features). So, if a person is informed on the advantages of the DB's, there shouldn't be too much hankering over whether their project is in need of mSQL or not.
Is there still a place for mSQL? (Score:1)
But what has mSQL done? Well, with 2.0 they added keys and became a sort of stable. They also created their own web scripting language (Lite/w3-sql) which came out before PHP became popular but since the early development of PHP it has looked like a relative but a younger brother at best. All this and they have always charged $200 per license. And the last release was Aug 1999.
So this leaves me with the big question, what are they going to do to be competitive? I suppose they could be but I don't know what it would take. For starters they will need to become truely open source because there is no other way they could develop fast enough. Do they have plans that are new and revolutionary? Or do they just intend to clean up their code and expect all thier former users that have given up on them and left for greener pastures to return?
I used mSQL 2.0 before I learned about MySQL and realized that it was faster (in almost everything), more stable, more feature rich, and free for web servers. Since then MySQL has improved a lot while mSQL has only had maintenance releases to the 2.0.x tree. They have fallen very much behind it will be interesting if they just pretend that they are on par or if they catch up. Good luck to them, they have a very uphill climb ahead.
Re:wahooO! (Score:1)
Why both are far behind the competition. (Score:1)
Lack of integrity constraints (like FKs) is a good example why both mSQL and MySQL blow chunks, compared to Interbase [borland.com]. The MySQL folks give their reasons [mysql.com] not support FKs, but IMHO they are a load of crap.
In my 6 years of developing database applications (Oracle, Sybase, Interbase), lack of FKs is the #1 reason why databases contain unclean data. The MySQL approach of 'let the developer' worry about it is assinine - especially if you have multiple interfaces to insert / update data in your database (e.g., a web interface and a traditional client-server interface).
The only Good Thing (tm) everyone on /. says about MySQL is that it is 'fast'. Interbase seems just as fast a MySQL on my Linux box. (I have never timed their query response times and I would appreciate any published comparisions to dissuade me.
"Fat, drunk, and stupid is no way to go through life."
Re:Why both are far behind the competition. (Score:1)
Suited for a small amount of data... LDAP anyone? (Score:1)
Re:why? (Score:1)
Ironic (Score:1)
Funny you shound say that, given that the only way you can get transactions in mysql is by using bdb (a.k.a. sleepycat's berkeley db) tables. When was the last time you looked at berkeley db? -- it's a lot more than a simple on-disk hash or btree. Take transactions for instance, libdb prvide's 'em, mysql just makes use of 'em.
It's funny, one of the questions in sleepycat's FAQ is "does berkeley db support an sql interface?". Once TCX calls 3.23 stable, they can change this to "Yes!".
wahooO! (Score:1)
Erk! (Score:1)
msql NEEDS to be free, or it won't survive. Anyone wanting speed -> mySQL. Completeness -> pgsql. Bugs -> Btrieve. Volume -> DB/2. Logo -> Oracle.
What niche has msql got?
Great, whatever. (Score:1)
The press release, before it gets slashdotted (Score:1)
For Immediate Release
Hughes Technologies re-enters the market and prepares to release the third generation of the Mini SQL database software.
In the early months of the year 2000, certain matters that are internal to the company forced it to suspend all activities associated with its primary product, Mini SQL. As of the 1st of January 2001, those matters have been resolved and the company is now preparing itself to start offering the products and services for which it was known.
"Our absence from the market has been disappointing for both our user base and ourselves." stated David Hughes, Managing Director. "Although we left the product available from the web site and didn't charge anybody who decided to use it, the lack of continued development and technical support has certainly hurt our users. In the next few weeks our operation will be back to full speed and we hope that users of our products will be happy with the software and support once again."
From the first of January, the development team has been working feverishly to prepare the first public release of the third generation mSQL product. A complete source code audit has been undertaken and the software has been modified extensively to improve it's underlying quality and stability. "Virtually every line of code has been inspected during the audit. The result is that the source has been modularised and rationalised to improve stability, reliability, and our ability to further enhance the software" says Hughes. Further details of the many enhancements made to the software will be made available on the web site at www.Hughes.com.au.
With the development team now back into full operation, the support and administration side of the company will start public work as of the 1st of February 2001.The release schedule for the mSQL 3.0 starts with an initial public release on the 15th of February 2001.
why? (Score:2)
so, why do we need an updated msql? i know, i know, open-source competition and all that. but really. who's going to use this?
--
Market Saturation ? (Score:1)
There are more RDBMS engines than one can shake a stick at. Between MySQL, Postgres, Oracle, Informix, Microsoft SQL Server, etc. it's amazing there is room for more of nearly the same product.
Well, if the performance is there I'll be the first one to switch over. Good Luck.
Competition is not good in Open Source (Score:1)
Well, in my opinion, the idea of competition neing good for software development id also outdated. Nothing would make me happier if, instead of halving a choice between half a dozen different poorly implemented solutions, there was just one excellent solution. The best open source projects have a monopoly, and suck all the development effort for that field - The Kernel and Apache for example.
Why do we need several different versions of SQL to be on the go? It would be far better if there were just one, and the quality of the product would improve also.
If only this were to happen across the board.
Watch me control my enthusiasm... (Score:1)
I remember when I used to use mSQL for the database backend of a site. Complete pain in the a$@!^. I remember having to write C-based scripts (there may have been perl or PHP interfaces at the time, but definitely not available from Hughes directly...). Left too much of a bad taste in my mouth, especially given MySQL works much better, is more featureful, and has an open source version to boot.
I don't see what a new version is going to bring to the table (they certainly don't tell you much on the site, and neither does the antelope :-). Then again, I may just be cynical. :-)
Re:Competition is not good in Open Source (Score:2)
Competition and natural monopolies are not mutually exclusive concepts. The kernel and Apache have natural monopolies because they were on the point, and continue to advance to the satisfaction of their users. If they were to falter, it is competition that would bring forth a competitor to topple them. Aside from HURD and other ossible kernel competitors, there exist multiple minor kernel forks as patches and development continues on old branches of the tree, so Linus' kernel really doesn't have a stifling monopoly that prevents competition as you imagine.
Programs can also exist as monopolies within a certain field, while losing out to another program in a different field. For example `ls' reigns supreme in the linux desktop world, while `busybox' holds a relative monopoly for embedded devices. Real or imagined, there exists a perception of multiple playing fields for SQL databases, and until a given database gains enough momentum in all of these fields to naturally draw mindshare and become a monopoly, it does no good to browbeat competitors under the banner of `Unity at All Costs'.
Re:Forget it, guys.... (Score:1)
really though. if you want someone to change the name it should be mysql. msql has been around alot longer than mysql.
use LaTeX? want an online reference manager that
Re:wahooO! (Score:1)
--
Re:Market Saturation ? (Score:2)
------------
a funny comment: 1 karma
an insightful comment: 1 karma
a good old-fashioned flame: priceless
Re:Why this Matters (Score:1)
OpenVMS performance barrier (Score:1)
Since Compaq's acquisition of DIGITAL and it's cash-cow OpenVMS, they have invested a small sum of money to integrate a more unix-like feel into the operating system which is apparent in version 7.3.
Responding to your post, I must inform you that not only is using DBI on OpenVMS a good way to increase performance, neither is using OpenVMS at all.
Especially on a three-node VAXstation cluster.
Re:Why both are far behind the competition. (Score:1)
I agree. But what is the value of the data in the database (integrity) relative to the importance of getting it in there (speed)?
I am biased because the databases I build contain data that is valuable, so it is always a requirement that data is not corrupted.
How do you like PG? I compiled the database, but never built anything with it.
"Fat, drunk, and stupid is no way to go through life."
Re:OpenVMS performance barrier (Score:1)
Larry! It's so good to see you here on Slashdot at last, finally abandoning the scourge that is Usenet. Soon, you'll join us on the darkside. You will join me and Dan D. in our exclusive use of Windows 2000...
Re:Only a-l and n-z are left. (Score:1)
about David Hughes (Score:2)
mSQL rocks (Score:1)
I wonder how many people who set up stuff using MySQL and others really need any functionality that isn't in mSQL?
M$ SQL's niche (Score:1)
One thing that MS SQL does have going for it is the most ANSI-compliant syntax I've seen in a while. Oracle will choke if you hand it:
select Company.CompanyName, Contact.ContactName from Company left join Contact on Company.CompanyID = Contact.CompanyID where Company.CompanyName like 'Acme%' Oracle uses some arcane outer join syntax I can't even remember off the top of my head. I've written a crapload of Transact-SQL and some (more recent) PL/SQL before though.Re:Erk! (Score:2)
Re:Competition is not good in Open Source (Score:1)
Competition. What is the point to improvement if there isn't something better out there?
Re:Erk! (Score:1)
Re:Competition is not good in Open Source (Score:1)
Re:why? (Score:3)
Re:why? (Score:2)
Thanks
Bruce
Re:Competition is not good in Open Source (Score:1)
Oracle
MSSQL
Progress
DB2
Etc...
That's plenty of comptetion I think.
One improvement... (Score:2)
(Not that I didn't find it funny, but I thought it was somewhat inappropriate for a corporate website, ya know? :-)
Re:Why this Matters (Score:1)
Only a-l and n-z are left. (Score:4)
Beware though, several names should be reserved: Linus gets lSQL.
oSQL nSQL and fSQL go to OpenBSD, NetBSD, and FreeBSD respectively. Apple will want aSQL, which will actually just be fSQL with the first letter changed. Stallman will write GNUsql, which much to his chagrin, will be called gSQL.
Mircrosoft will sue Hughes, claiming that the m in mSQL stands for Microsoft.
And I want bSQL. Cause its just BS.
Re:wahooO! (Score:1)
Re:Forget it, guys.... (Score:1)
-Moondog
Re:wahooO! (Score:1)
Sure man, if you say so. You don't mind paying for my toilet paper from now on, do you?
Linux? (Score:3)
By "The Kernel", do you mean Linux? Remember that Linus choice to create a Linux, even though Minix and FreeBSD already existed. If he had felt, like you do, that competition is a waste of time, there would be no Linux today. If software monopoly is so great, then why was Minix (or Windows) not good enough to meet Linus' needs way back when?
And not all "open source competition" is from other open source projects. Linux 2.4 has performance improvements because of competition from Windows 2000. Apache 2.0 is introducing a new threading model because of competition from IIS.
Re:wahooO! (Score:1)
Is this the same type of competition that Linux gives Windows?
It's alive... (Score:4)
"Yeth, Mathter."
"And now the axe! I should have listened to old man Ellison when he said you had to properly dispose of these things."
"Thall we be burning it, Mathter?"
"One step at a time, Igor. To properly dispose of a vampire SQL package, you have to make sure none of the embers escape, or we'll have to deal with this all over again!"
Why this Matters (Score:3)
The reason to use mSQL is to store a small amount of non-essential data for extremely rapid retrieval. It is easy to use, and, for the record, does have PHP driver support. Not that there is that much to support anyway :)
Seriously, though, if you're going to criticize mSQL, you have to be willing to acknowledge that the only leg-up MySQL has (before the row-level lock gets finished) on mSQL is the ability to write functions. And it doesn't even have a procedural language, just C-functions! So don't stand all high-and-mighty looking down on mSQL from your MySQL pedastal - it's not that high off the ground.