News for hackers. Stuff that matters.
Re:Implementing State Machines in PostgreSQL by mercer on Monday July 31, 2017 @11:21AM (#14892801)
Could you give some specifics as to what kind of stuff typically needs refactoring if you switch storage layers?
Re:Implementing State Machines in PostgreSQL by dspillett on Tuesday August 01, 2017 @05:56AM (#14899132)
Even if you stick to the SQL standard as much as possible engine specific syntax almost always creeps in unless you routinely test against all target systems from the start (which you might not be able to justify the time to do on many projects where being platform agnostic is not initially a core high-priority requirement).

And even where there are no feature or syntax issues there may well be optimisation differences. For instance going from MSSQL to postgres you might hit a significant difference with CTEs because MSSQL can perform predicate optimisations through them but postgres doesn't - this might mean core queries need to be refactored significantly for performance reasons (to avoid extra index or table scans) if not functional ones. (not intending to pick on postgres here, I'm sure there are similar examples in the other direction and between other engines, but this is the most significant example that immediately springs to mind).

Re:Implementing State Machines in PostgreSQL by edoceo on Monday July 31, 2017 @11:36AM (#14892930)
Stored Procedures, any use of the RDBMS SQL extensions (eg: BETWEEN)
Re:Implementing State Machines in PostgreSQL by jsjohnst on Monday July 31, 2017 @02:47PM (#14894814)
I partly answered your question in a comment above. If you'd like me to go more in depth, happy too!