Timeline for PostgreSQL 15: ERROR: operator is not unique: unknown || double precision
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2023 at 16:06 | comment | added | Laurenz Albe | I understand. But that doesn't rule out the second option. Being unambiguous about data types can actually prevent undesired behavior of the query. I can understand that the pain to fix all your SQL statements is great, but it might be the better option in the long run. | |
| Nov 23, 2023 at 15:47 | comment | added | Athris | Other database allow implicit cast. We are just introducing PostgreSQL and have now encountered the problem mentioned above. | |
| Nov 23, 2023 at 15:38 | comment | added | Laurenz Albe | Pshaw. Don't tell me that other databases don't understand queries that use data types correctly. no database insists on you concatenating strings with numbers... | |
| Nov 23, 2023 at 15:32 | comment | added | Athris | Option 2 cannot be implemented because the queries are used in an environment that includes several database types. | |
| Nov 23, 2023 at 15:12 | history | answered | Laurenz Albe | CC BY-SA 4.0 |