Thanks for the quick reply Tim, see my other posts. FB is probably the most SQL99 standard SQL DB, so usually the standard statements work. I think FB 2.1 is going to support all 3 different limiting syntax. I changed it to work with ROWS.
On May 5, 2:49 pm, Tim Chase <[EMAIL PROTECTED]> wrote: > >> The real problem is when I try to access the database. I get > >> stack trace below. It looks like it is trying to use the > >> LIMIT keyword incorrectly. > > As best I can tell, Firebird doesn't support the SELECT ... LIMIT > x OFFSET y" notation, but rather uses "SELECT FIRST x [SKIP y] > ..." as detailed here: > > http://scott.yang.id.au/2004/01/limit-in-select-statements-in-firebird/ > > (and I concur on the author's "[Firebird's] documentation is > lacking" as after dilligent seeking on the FB site, I couldn't > find a simple BNF grammer of their SQL flavor) > > You'd have to create your own backend that uses this notation for > slicing. At least FB does have such limit/offset notation, > unlike SQL Server for which it's a pain. > > -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
