AFAICT, PostgreSQL is still capable of doing the time warp, meaning that you can rewind a live table back to just before the DROP and recover the DROPped information.
GPL means that you can allow others into your party. Putting improved MIT/BSD software out only happens if the developer is charity-minded themselves; GPL makes charity-minded behaviour mandatory. This means that you can release something with the expectation of seeing more of the improvements made by others coming home to roost, and knowing that no competitor can out-develop you.
The DB can work with the OS in the same way as it does raw partitions: this gives it reasonable abstraction but retains the performance boost of knowing stuff about the DB contents. With the DB knowing how best to treat stuff in the DB and the OS knowing how best to get stuff to and from a drive, the potential for performance gains is greater than just that of the DB knowing what the info is doing.
There are other examples to consider as well, for example, Windows apps often run twice as fast on the same machine under Win4Lin as they do natively, because Linux task switching, memory management and (yes) cacheing is streets ahead of Windows 9X. In this case, knowing how to deal with the hardware well is more important than knowing about internal structures.
With MS and a few others you just need the servername and dbname and it works.
Actually, with MS you only need the servername and it's as good as 0wn3d (-: and with the advent of SQLsnake, you don't even need that:-)
PostgreSQL is a lot more standard and complete than MySQL, outruns it in many practical situations (ie under enough load that anyone actually cares about performance) and is as easy to set up and use (if not easier) than MySQL; it also has simpler, clearer licencing. The mystery to me is why MySQL has done as well as it has in the face of all of this.
InterBase also seems to hammer MySQL pretty much across the board, but was a late starter. I'd expect to see it do some catching up as more of the application languages abstract their DB interfaces, detaching the DB choice somewhat from application programming and so allowing the DB to be chosen on merit rather than I-was-here-first.
More and more scripting languages (PHP, PERL, Ruby, Python, TCL) are working through generalised DB interfaces; there is less and less difference (often none) between backend DB's from an application programmer's PoV.
In some cases the backend DB needn't even be SQL (great news for tiny high-performance web apps), but where the backend DB does stick closely to SQL standards the applications produced with it are more likely to be portable and scalable.
PostgreSQL does replication. PostgreSQL thrashes Oracle performance-wise in many situations. PostgreSQL costs just a little less than Oracle to buy and house. PostgreSQL was one of the first kids on the GPL block. The conclusion about a niche for SAB seems pretty much inevitable.
If PostgreSQL could magically don an Oracular CIO-level reputation, the bottom half - or more - of the Oracle market would evapourate in a few short years.
I'd be interested in RainingData (<span face=poker>now there's a truly inspired name change</span>) nee Pick GPLing their MultiValue database. Overall, a pig to use and maintain compared with something like PostgreSQL, but it still does some neat tricks and has a reasonable community around it.
Of course, having Mandrake package it probably took all the fun away, but it was no harder than Windows' ODBC manager to set up, and you get a good deal more control over the process if you want it.
Not sure what business a database has driving a tape deck directly anyway; one would hope that as far as possible the DB would let the OS figure such nightmares out. That's what OSes are for, although Oracle certainly seems to have forgotten that.
PostgreSQL does transactions, hot backups etc, would you consider switching to it?
Better players don't shaft the other players at every opportunity.
He's using whatever power he has to get more power, the dollars are nearly incidental.
Again I say, have a careful look at the charities he's giving to, the conditions attached, and so on. He's more than getting value for money, and that makes it not a donation any more.
Nett worth is a linear measure, donation is time-dependent. A typical single mother will have a net worth of close to zero dollars (and not always on the positive side of that), so anything she gives would by your measure be essentially infinite.
Try rating Trey's donations against his income and when you're finished doing that, have a closer look at the charities he gives to and how he does that giving.
Y'know, if you hadn't over-reached yourself and used that word `all' in front of `legal', you might have escaped unpunished for that one sentence. However, read this and weep. There's a lot more elsewhere.
Sorry, what was it that your clueless comments prove?
There are a lot of knock-on problems which are often buried under a wave of zealotry. Not the least of which is being totally controlled by foreign seed suppliers.
Got started in AlphaBASIC on an AM-100 in 1980, helping out the odd business, did some work for Computer Choice, a retail computer store in West Perth, 1981-82, on the likes of Apple ][,//e,//c,///, Lisa, Macintosh, Hitachi Peach, NAC APC II thru IV, Osborne-1, KayPro II thru 10 etc (including Z80 assembler work in a display manager for K2s, whose only screen atrribute was `blink' - top choice, and an interactive realtime blast-the-spaceships game written in Z80 assembler for the O1 to see if I could find a use for the CPIR instruction). All sorts of stuff. Wrote and supported ForTran and RatFor programs under RSX-11-M-PLUS on PDP-11/23 and/73 systems, also touched BASIC-PLUS-TWO apps and the DECUS C compiler. Spent roughly eight years, on and off part time, working for ChiroSoft producing front-desk apps for Chiropractors in FoxBase Plus, later FoxPro, gave it up when Microsoft bought them - that included a software barcode scanner written in assembler and a record/replay for DOS and FoxPro written in asm and C. Built a FoxPro2-based order processing system for my brother in law which ran on a 386DX16 with a full-height full-length RAM board to give it a staggering 2MB of RAM. First Linux exposure was Slackware on a 386SX20 laptop with 2MB of RAM (which I still have, but the 100MB HDD has since died). Currently tinkering with LTSP systems and wanting time to write a 3D toy train sim for my son's 3rd birthday in 3 weeks. Lots of other stuff in between those.
You still have no particular reson to trust me, but at least you have a smattering more background. Why do you want to know?
Slashdot Mirror
Ask the OS how big the tapes are; in case of uncertainty, waste the last few meters of tape.
AFAICT, PostgreSQL is still capable of doing the time warp, meaning that you can rewind a live table back to just before the DROP and recover the DROPped information.
Like, `mortgage your house so you can buy a better model of our car?' Not single-mindedly ambitious at all, are they? (-:
Talk about help from unexpected quarters!
What can I say? `Me, too?' Thanks for correcting my licencing blue.
To grandparent: true, my blue.
GPL means that you can allow others into your party. Putting improved MIT/BSD software out only happens if the developer is charity-minded themselves; GPL makes charity-minded behaviour mandatory. This means that you can release something with the expectation of seeing more of the improvements made by others coming home to roost, and knowing that no competitor can out-develop you.
The DB can work with the OS in the same way as it does raw partitions: this gives it reasonable abstraction but retains the performance boost of knowing stuff about the DB contents. With the DB knowing how best to treat stuff in the DB and the OS knowing how best to get stuff to and from a drive, the potential for performance gains is greater than just that of the DB knowing what the info is doing.
There are other examples to consider as well, for example, Windows apps often run twice as fast on the same machine under Win4Lin as they do natively, because Linux task switching, memory management and (yes) cacheing is streets ahead of Windows 9X. In this case, knowing how to deal with the hardware well is more important than knowing about internal structures.
http://techdocs.postgresql.org/techdocs/settingupr serv.php
Actually, with MS you only need the servername and it's as good as 0wn3d (-: and with the advent of SQLsnake, you don't even need that :-)
PostgreSQL is a lot more standard and complete than MySQL, outruns it in many practical situations (ie under enough load that anyone actually cares about performance) and is as easy to set up and use (if not easier) than MySQL; it also has simpler, clearer licencing. The mystery to me is why MySQL has done as well as it has in the face of all of this.
InterBase also seems to hammer MySQL pretty much across the board, but was a late starter. I'd expect to see it do some catching up as more of the application languages abstract their DB interfaces, detaching the DB choice somewhat from application programming and so allowing the DB to be chosen on merit rather than I-was-here-first.
More and more scripting languages (PHP, PERL, Ruby, Python, TCL) are working through generalised DB interfaces; there is less and less difference (often none) between backend DB's from an application programmer's PoV.
In some cases the backend DB needn't even be SQL (great news for tiny high-performance web apps), but where the backend DB does stick closely to SQL standards the applications produced with it are more likely to be portable and scalable.
PostgreSQL does replication. PostgreSQL thrashes Oracle performance-wise in many situations. PostgreSQL costs just a little less than Oracle to buy and house. PostgreSQL was one of the first kids on the GPL block. The conclusion about a niche for SAB seems pretty much inevitable.
If PostgreSQL could magically don an Oracular CIO-level reputation, the bottom half - or more - of the Oracle market would evapourate in a few short years.
There are several other good databases around. InterBase looks pretty excellent.
I'd be interested in RainingData (<span face=poker>now there's a truly inspired name change</span>) nee Pick GPLing their MultiValue database. Overall, a pig to use and maintain compared with something like PostgreSQL, but it still does some neat tricks and has a reasonable community around it.
Of course, having Mandrake package it probably took all the fun away, but it was no harder than Windows' ODBC manager to set up, and you get a good deal more control over the process if you want it.
Not sure what business a database has driving a tape deck directly anyway; one would hope that as far as possible the DB would let the OS figure such nightmares out. That's what OSes are for, although Oracle certainly seems to have forgotten that.
PostgreSQL does transactions, hot backups etc, would you consider switching to it?
Better players don't shaft the other players at every opportunity.
He's using whatever power he has to get more power, the dollars are nearly incidental.
Again I say, have a careful look at the charities he's giving to, the conditions attached, and so on. He's more than getting value for money, and that makes it not a donation any more.
...control over their own crops.
Or does that go too much against the grain?
The less said about that, the better.
Nett worth is a linear measure, donation is time-dependent. A typical single mother will have a net worth of close to zero dollars (and not always on the positive side of that), so anything she gives would by your measure be essentially infinite.
Try rating Trey's donations against his income and when you're finished doing that, have a closer look at the charities he gives to and how he does that giving.
Y'know, if you hadn't over-reached yourself and used that word `all' in front of `legal', you might have escaped unpunished for that one sentence. However, read this and weep. There's a lot more elsewhere.
Sorry, what was it that your clueless comments prove?
We're talking second and successive generations here. You get all manner of interesting recombinant effects.
There are a lot of knock-on problems which are often buried under a wave of zealotry. Not the least of which is being totally controlled by foreign seed suppliers.
...I don't support that, because it's not GPL and has tainted my kernels? (-:
...I have farming rellies.
It was a nice, neat margin. For the purposes of illustration, it could have been 50% and still made no practical difference.
Got started in AlphaBASIC on an AM-100 in 1980, helping out the odd business, did some work for Computer Choice, a retail computer store in West Perth, 1981-82, on the likes of Apple ][, //e, //c, ///, Lisa, Macintosh, Hitachi Peach, NAC APC II thru IV, Osborne-1, KayPro II thru 10 etc (including Z80 assembler work in a display manager for K2s, whose only screen atrribute was `blink' - top choice, and an interactive realtime blast-the-spaceships game written in Z80 assembler for the O1 to see if I could find a use for the CPIR instruction). All sorts of stuff. Wrote and supported ForTran and RatFor programs under RSX-11-M-PLUS on PDP-11/23 and /73 systems, also touched BASIC-PLUS-TWO apps and the DECUS C compiler. Spent roughly eight years, on and off part time, working for ChiroSoft producing front-desk apps for Chiropractors in FoxBase Plus, later FoxPro, gave it up when Microsoft bought them - that included a software barcode scanner written in assembler and a record/replay for DOS and FoxPro written in asm and C. Built a FoxPro2-based order processing system for my brother in law which ran on a 386DX16 with a full-height full-length RAM board to give it a staggering 2MB of RAM. First Linux exposure was Slackware on a 386SX20 laptop with 2MB of RAM (which I still have, but the 100MB HDD has since died). Currently tinkering with LTSP systems and wanting time to write a 3D toy train sim for my son's 3rd birthday in 3 weeks. Lots of other stuff in between those.
You still have no particular reson to trust me, but at least you have a smattering more background. Why do you want to know?
...and thanks for your support. (-:
:-)
Pity I have karma to burn. Wanna hold a Karma Bonfire? (-: I have a list of topics
Both Bill and Microsoft fail this measure miserably regardless of tax deductability arguments.