On Tue, Jun 28, 2011 at 9:26 AM, akaariai <[email protected]> wrote: >> this looks quite non-portable > > How? The CASE statement is specified in SQL standard, and it is > implemented in all database I have used.
i might be totally wrong (wouldn't be first time..) but i've found myself having to adapt to local dialects almost every time i see some SQL inside a function, especially on mysql and sqlite. maybe it's because of the bad quality of code i tend to see (typically originating from hand-coded mssql accesses deep within an excel sheet), but seeing CASE also rings my "i'll need an extra week just for this" alarm. then again, i'm soooo far from being an SQL portability expert. it's just something i've (reluctantly) done a few times -- Javier -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
