![]() According to that user, either will do, though the team’s experience should be the deciding factor. “Evanelias” discloses that he worked profusely on MySQL and may be biased toward it but admits it is less “batteries included”. “CameronNemo” adds that the goal is to lure developers into using what they think is liberal source code and then back charging them after an audit. In his opinion, MySQL sneakily changed the driver licensing scheme to be more restrictive. ![]() User “gtsteve” says that PostgreSQL and MySQL have different licensing for client-side drivers. According to that user, haphazard data type use in MySQL can lead to “polluting data”. User “nmpennypacker” adds that PostgreSQL enforces data types natively, which MySQL does not. That user notes that ease of deployment does not correlate with long-term feasibility. ![]() “Madhadron” recommends developers use what they are more familiar with. User “jerrytsai” says PostgreSQL has better features for analyzing data in a scientific sense. User “matthewmacleod” recommends using PostgreSQL as the default RDMS unless there is a reason not to. 2019 PostgreSQL vs MySQL discussionĪ 2019 Hacker News thread on PostgreSQL vs MySQL provides more insights into the developer consensus over which is better. When that assumption fails them, they experience a series of outages and errors. In his experience, end-users assume that MySQL replication features will operate as intended without planning or oversight. In response to kaamos’ feature wish list, user “fusiongyro” replied that advanced replication strategies in MySQL cause “hair loss and divorce” due to faulty distributed consistency. Kaamos notes that those features are “huge for people who design and operate the busiest websites on the internet, (w)hich is probably why MySQL still shines in that field.”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |