6 ms·
I like the sample data they have used: id first last birth_year 1 Blaise Pascal 1623 2 Gottfried Leibniz
by zeeshanm 10y ago
I like the sample data they have used:
id first last birth_year
1 Blaise Pascal 1623
2 Gottfried Leibniz 1646
3 Emmy Noether 1882
4 Muhammad al-Khwārizmī 780
5 Alan Turing 1912
6 Srinivasa Ramanujan 1887
7 Ada Lovelace 1815
8 Henri Poincaré 1854
- antonius 10y agoMind explaining the significance? I didn't pick up on it.
- digitalinfinity 10y agoThey're all famous mathematicians
- houli 10y agoThey're all famous scientists/mathematicians.
- praccu 10y agoold mathematicians
- klancaster 10y agoNo, dead mathematicians
- muddyrivers 10y agoIt caught my eyes as well. Like it very much.
- deleted 10y ago[deleted]
- muddyrivers 10y agoMy understanding is that it is very diversified in terms of race, gender, ethnicity, sexuality identification, etc. Make no mistake, they are all great mathematicians and deserve a place in math pantheon.
- rspeer 10y agoExcept it's MySQL, so by the time you read it out it says: id first last birth_year 1 Blaise Pascal 1623 2 Gottfried Leibniz 1646 3 Emmy Noether 1882 4 Muhammad al-Khw�rizmī 780 5 Alan Turing 1912 6 Srinivasa Ramanujan 1887 7 Ada Lovelace 1815 8 Henri Poincaré 1854 (I know, I know. It is possible to configure MySQL encodings correctly. And given that they've put a lot of engineering thought into choosing MySQL, they certainly have.)
- codedokode 10y agoI used both Postgres and MySQL and in my opinion encodings are more difficult to setup with Postgres. You need to change some "template" when creating a database to use unicode. Otherwise it will use latin1. I do not even understand what a database "template" is, how it is related to encodings, and why it is so overcomplicated. In MySQL there is no templates and you can change the encoding of a table at any time using ALTER TABLE statement. And in cloud IDEs like c9.io you cannot use unicode collations in Postgres because they need to be installed separately and they are not installed.
- rosser 10y agoSo ... you'd rather have a database with mixed encodings, on a table-by-table basis? Ugh.
- pritambaral 10y agoYou certainly don't need to change any templates when creating a database, CREATE DATABASE and createdb both support specifying the encoding. Changing encoding of a table (or a database after creation) is usually not a wise thing to do; since the db engine is not going to go over all the data and convert it anyway, so if your data is corrupted now it will remain corrupted. If one simply needs to tell the DB to treat the data differently without worrying about data conversion, the encoding of a database is stored in `pg_database` and can be changed with an UPDATE query. And this is all from the official documentation. I'm not a Postgres expert.
- sunstone 10y agoNo love for Kurt Godel I see.