On Thursday, August 20, 2020 at 1:45:59 PM UTC-7, Anant M wrote: > > That makes sense. Really appreciate your help! I am testing the > disable_quoting feature. I think the sqlite database was created with > case-insensitivity in mind so I don't think there should be any issues > (does not seem like overlapping or spaces are a thing in this db). I think > currently the idea is to migrate the sqlite database to a psql database so > shouldn't be an issue to disable quoting? >
This depends. PostgreSQL probably has far more keywords than SQLite, so identifiers that may not need quoting on SQLite may need quoting on PostgreSQL. However, if you aren't using an identifier that requires quoting, disabling identifier quoting may work fine. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/40dc525a-77c1-4120-8228-7c37edc77450o%40googlegroups.com.
