+- Python Forum (https://python-forum.io)
+-- Forum: Forum & Off Topic (https://python-forum.io/forum-23.html)
+--- Forum: Bar (https://python-forum.io/forum-27.html)
+--- Thread: Interesting observation on MySQL (/thread-2201.html)
Pages:
1
2
Interesting observation on MySQL - Larz60+ - Feb-26-2017
I'm reading a book on PostGIS, and found this paragraph quite humorous, as it
fits my thoughts perfectly:
Quote:MySQL has had elementary spatial support since version 4, but as a database MySQL is
handicapped by its lack of a powerful SQL engine. Its primary audience is still developers who
are looking for a database that will store something, rather than do something.
from PostGIS in Action (Regina O. Obe & Leo S. Hsu, Manning Publishing)
RE: Interesting observation on MySQL - wavic - Feb-26-2017
Everyone write books these days.
RE: Interesting observation on MySQL - j.crater - Feb-26-2017
(Feb-26-2017, 04:48 AM)wavic Wrote: Everyone write books these days.
This reminds me of a saying (it has nothing to do with @Larz's post):
It is a good idea to read very old books, cos fools weren't able to write back in the time.
RE: Interesting observation on MySQL - wavic - Feb-26-2017
I am not a programmer neither a teacher. But you have to have skills for both.
I remember my math teacher when I was in the high school. She explained so well that there was no need for me to study. Just to listen to her.
Books? When I was a student I had this C programming book and it was written so well. I discovered how the computers work, so when I bought a Win XP book it was useless for me. I just looked at the CRT monitor and knew what I was watching.
As regards to C programming... Well, it was easy to follow the book almost to the end. I don't remember C programming from those days. I didn't continue with it. But The knowledge, the big picture how the thing works remained.
RE: Interesting observation on MySQL - Larz60+ - Feb-26-2017
My point was that the author was on the money.
If you compare MySQL to PostgreSQL, it's quickly clear that
you are comparing sand to Mt Everest.
RE: Interesting observation on MySQL - wavic - Feb-26-2017
Yes, I've got it. I can't stand such a things. But there are people and people. However, one can learn even from the waisted money for the book. There is no bad experience.
RE: Interesting observation on MySQL - Larz60+ - Feb-26-2017
Quote:waisted money
Really?
RE: Interesting observation on MySQL - wavic - Feb-26-2017
The quoted is from the book? MySQL was developed from many years, so how can lack of good SQL engine...
I am more interested for sqlite since you don't need to start a server to use it
RE: Interesting observation on MySQL - Larz60+ - Feb-26-2017
They all have their purpose.
PostgreSQL is free.
It is also on par with Oracle
When it comes to GIS, you won't find many of these 'out of the box' features that come with PostgreSQL
- Support for GeoJSON and KML
- Geometry-processing functions that go far beyond basic geometric operations
- 3D and topology support
- Operations (over 150 of them) for working with raster and vectors in tandem
- Many conversion operations for converting between raster and vector data.
On PostgreSQL itself:
- it is the most advanced open source database, period.
- It's speed and functionality is on par with Oracle.
- It can and does power databases terabytes in size.
- It is extensible.
I have had extensive experience with Oracle DBMS used in one of the most data intense environments (Telecommunications)
It is still one of the best available for most any extremely high volume data task, but only large corporations can afford
it. PostgreSQL can come close, and maybe even match it's performance, can run on as many cores as you can give it, and
is free.
I'm a fan, and have been for a long time.
Sqlite is very good, and I use it. One thing I especially like is the one file for everything.
I haven't ever tried to use it with extremely high volume data.
RE: Interesting observation on MySQL - nilamo - Feb-26-2017
mysql isn't that bad if you use innodb. But it's pretty bad with the default engine. I do agree that postgres is just better most of the time, though.
It's been a while since I've used either, though... we use sql server at work.