database - Android SQLite fast Date between search -


i have huge performance issue when comes sqlite query date ranges.

in application have database couple of thousands of records of sites. these sites visitable not whole year. each of sites can define 3 ranges in is visitable. therefore created sqlite table following columns: open1, close1, open2, close2, open3 , close3 (amongst others)

application users can enter time range in want visit site, e.g. 2014.01.01 - 2014.01.07

now when perform search without restricting time pretty fast. when use opening time search criteria, search takes 7 seconds on fast emulator. not want test on real device :)

the entries in columns open , close of type datetime , like: 2014-01-01

my current query follows:

    select open1,close1,open2,close2,open3,close3 sites (       ( ( strftime('%y-%m-%d', '2014-01-01') between open1 , close1 ) , ( strftime('%y-%m-%d', '2014-01-07') between open1 , close1 ) )       or       ( ( strftime('%y-%m-%d', '2014-01-01') between open2 , close2 ) , ( strftime('%y-%m-%d', '2014-01-07') between open2 , close2 ) )       or       ( ( strftime('%y-%m-%d', '2014-01-01') between open3 , close3 ) , ( strftime('%y-%m-%d', '2014-01-07') between open3 , close3 ) )     )

is there simple way improve performance?

notice: tried using utc values in long format open , close not debuggable.

thanks in advance help!

i not sure if more efficient can not hurt simplify query :

( ( strftime('%y-%m-%d', '2014-01-01') between open1 , close1 ) , ( strftime('%y-%m-%d', '2014-01-07') between open1 , close1 ) )

is equivalent :

( strftime('%y-%m-%d', '2014-01-01') >= open1 , strftime('%y-%m-%d', '2014-01-07') <= close1 )

as long first date ('2014-01-01' in case) before second ('2014-01-07'), i.e. have :

open* <= first <= second <= close*


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers ...
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());...
Read more