SQL migration from MySQL to PostgreSQL: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
#change LIKE to ILIKE : LIKE is not case-sensitive in MySQL, but in PostgreSQL it is !! query will then return an error in MySQL | #change LIKE to ILIKE : LIKE is not case-sensitive in MySQL, but in PostgreSQL it is !! query will then return an error in MySQL | ||
#see also [[Postgresql vs Mysql]] | #see also [[Postgresql vs Mysql]] | ||
#automatic conversation (which tool?) : suspected: turned the type of some fields (select list?) into boolean, i.e. the type "select list" needs to be changed before or treated in another way | #automatic conversation (which tool?) : suspected: turned the type of some fields (select list?) into boolean, i.e. the type "select list" needs to be changed before or treated in another way, in tango.info affected: gender field which had allowed values of 1,2,9 - as in ISO 5218 - and NULL |
Revision as of 2022-10-29T15:44:54
- change LIKE to ILIKE : LIKE is not case-sensitive in MySQL, but in PostgreSQL it is !! query will then return an error in MySQL
- see also Postgresql vs Mysql
- automatic conversation (which tool?) : suspected: turned the type of some fields (select list?) into boolean, i.e. the type "select list" needs to be changed before or treated in another way, in tango.info affected: gender field which had allowed values of 1,2,9 - as in ISO 5218 - and NULL