News for hackers. Stuff that matters.
Re:Migrating 1200 databases from MySQL to Postgres by overcast on Wednesday August 16, 2017 @09:56AM (#15027466)
You should see the one here. An old flat file database monstrosity from the 80s, imported into oracle, complete with all of the duplicated data. It's the most non relational, relational database ever.
Re:Migrating 1200 databases from MySQL to Postgres by zimpenfish on Wednesday August 16, 2017 @09:57AM (#15027475)
Would a database stored in an XML file shared between 60+ clients over NFS beat that for monstrositiness?
Re:Migrating 1200 databases from MySQL to Postgres by overcast on Wednesday August 16, 2017 @10:11AM (#15027573)
Well, this is used now by about 4000 clients. So you be the judge. There is so many indexes, and spaghetti, just to make sure every possible "relationship" is accounted for. Amazing it works at all.

Just using an XML file is pretty crazy though.

Re:Migrating 1200 databases from MySQL to Postgres by cntlzw on Wednesday August 16, 2017 @10:10AM (#15027565)
How concurrent is that? Can't imagine how writing to the file is even achieved.
Re:Migrating 1200 databases from MySQL to Postgres by zimpenfish on Wednesday August 16, 2017 @10:47AM (#15027858)
"Badly". At least once a week someone managed to overwrite a change another client had just made. When I left, they were running a cron to copy it every minute as a "quick restore" when it happened.
Re:Migrating 1200 databases from MySQL to Postgres by shoo on Wednesday August 16, 2017 @10:14AM (#15027599)
maybe there is an email thread shared between all clients for acquiring / releasing the write lock on the xml file
Re:Migrating 1200 databases from MySQL to Postgres by K-Wall on Wednesday August 16, 2017 @11:17AM (#15028120)
Semaphore as a service Slack Chat bot.
Re:Migrating 1200 databases from MySQL to Postgres by noir_lord on Wednesday August 16, 2017 @03:39PM (#15030527)
Seen that.

Shared drive with excel files, people would shout at each other to 'release the lock'

Re:Migrating 1200 databases from MySQL to Postgres by zimpenfish on Thursday August 17, 2017 @05:55AM (#15035205)
Yeah, first real job had the customer database as a VB frontend onto an Access file shared over {whatever Win95 was using in 1996-97}. After a few snafus, the CS / Sales people learned that they had to single-task with the database.
Re:Migrating 1200 databases from MySQL to Postgres by abraae on Wednesday August 16, 2017 @10:48PM (#15033405)
That made me snort my coffee.
Re:Migrating 1200 databases from MySQL to Postgres by jboy55 on Wednesday August 16, 2017 @05:50PM (#15031681)
Lol, if it sent emails, I might know of such a system
Re:Migrating 1200 databases from MySQL to Postgres by toomuchtodo on Wednesday August 16, 2017 @10:26AM (#15027692)
This is a special level of hell.
Re:Migrating 1200 databases from MySQL to Postgres by noir_lord on Wednesday August 16, 2017 @01:24PM (#15029322)
I have 177 tables, 764 stored procedures and 44 joins.

Every single table has either a uniqid() or a UUID() which isn't the primary key (they all have incrementing integer keys) but is 'joined' on in code.

When he needs to 'join' he used coalesce() on selects.

Referential integrity doesn't exist.

Oh and the cherry on the shit sandwhich, we have four seperate systems that talk to this database written in 3 different languages (Java (Android scanners), C# (Factory scanners) and PHP (the main system).

So there is no way to accurately know which SP's are used by what without grepping the entire codebase looking for call <foo>.

The PHP is written badly in the old PHP pure procedural style running on an outdated version of PHP/Debian/MySQL.

Basically if you took the absolute worst approach to everything this would be the end result.

It's good fun!.