To be fair, what actually returned in the native environment in 1.5 seconds (I now realize) was only the 1st page worth; when I went to "last", it took about another 10 seconds to get all the records.
On Thu, Aug 13, 2009 at 10:51 PM, David Jenkins <[email protected]>wrote: > Thanks, Jeremy. > > I tried > > dataset = DB['SELECT * from getcrossdata(\'MSFT\', \'1986-03-13\', > \'2009-08-12\')'] > > where the raw SQL natively (i.e., in an isql session) takes about 1.5 > seconds to return the dataset, and using Sequel I killed it after about 2 > minutes. > > I then tried your syntax, and it was faster, but still took about 26 > seconds (according to Benchmark). Damn shame, it's so speedy when called > natively, even across the network. :( > > If anybody has any ideas, I'm all ears. > > TIA > > > > On Thu, Aug 13, 2009 at 10:32 PM, Jeremy Evans <[email protected]>wrote: > >> >> On Aug 13, 7:21 pm, dj <[email protected]> wrote: >> > I've got a stored procedure on a DB I'm accessing through ODBC (for >> > Sequel); when I use it natively, I use this syntax: >> > >> > Select * from getcrossdata('MSFT', '1986-03-13', '2009-08-12') >> > >> > (the store procedure, obviously, is 'getcrossdata', and it takes 3 >> > params, a varchar and 2 dates) >> > >> > Can you tell me what the equivalent syntax would be w/Sequel? I >> > understand there is no guarantee it will work. >> >> That looks like a set returning function and not a true stored >> procedure, but my experience with SQL server is limited. You could >> try: >> >> DB.from(:getcrossdata.sql_function('MSFT', '1986-03-13', >> '2009-08-12')).all >> >> Jeremy >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
