c# - Does multiple query block on single connection(SqlConnection)? -


i have sample data access method design below calls recursively:

public static void deleterecord(sqlconnection connection, string childids, string parentsheetname) {     using (var adapter = new sqldataadapter("...", connection))     {         //fill datatable         string newids = "...";         string newparentname = "...";          const string query = "delete table " +                               "where ids in (@ids) , parent = @parent";         //here's recursion takes place         deleterecord(connection, newids, newparentname);          using (var command = new sqlcommand(query, connection))         {             var parameters = new[] {                  new sqlparameter(...), new sqlparameter(...)             }             command.parameters.addrange(parameters);             command.executenonquery();          }    }

my questions are:

  1. (as practice) okay pass connection parameter?

  2. is okay put deleterecord method on task each time call it, there's no waiting time command execute query. (of course there's task.waitall(tasks) somewhere)

  3. on scenario number 2, connection block multiple queries sent on server? i've experienced sqlserver suspending queries if has heavy query executing. (connection pooling enabled default, i'm wondering if case here on item 3)

you cannot execute multiple statements concurrently on connection. if want execute multiple statements need use multiple connections. however, in case bad idea. need wrap deletion in transaction maintain database consistency. deleting items on separate connections cannot achieve transactional consistency.

you should think in sets, not items. pass items deleted @ once. see table-valued parameters details how achieve this. use single delete statement joins entire parameter set.


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