Something like this. The example is probably not very good as it doesn’t properly dispose objects but you get the idea. Here’s a cleaned up version: using (var connection = new SqlConnection(ConnectionString)) using (var command = connection.CreateCommand()) { connection.Open(); command.CommandText = “select id from test1; select id from test2”; using (var reader = command.ExecuteReader()) { … Read more
Transaction Script is definitely not an anti-pattern. From what I find about Transaction script, it is not object-oriented at all. You are right, it is not, indeed. That fact however doesn’t make it an anti-pattern. Although it is a procedural approach, indeed, it still has its right place in the series of business logic architecture … Read more
private data members are generally considered good because they provide encapsulation. Providing getters and setters for them breaks that encapsulation, but it’s still better than public data members because there’s only once access point to that data. You’ll notice this during debugging. If it’s private, you know you can only modify the variable inside the … Read more
I would claim that, like most things, its a sliding scale. There are things that we make that want to have the property of persistence. On one end of the scale is this thing having all of the guts, dependencies, and code that is custom built to persist just this one thing in its particular … Read more
The problem is that people are really sloppy with terminology. There are 3 important but distinct classes here: O(1) worst-case This is simple – all operations take no more than a constant amount of time in the worst case, and therefore in all cases. Accessing an element of an array is O(1) worst-case. O(1) amortized … Read more
Steven Devijver provided some good reasons for starting transactions even if the operations are only going read the database: Set timeouts or lock modes Set isolation level Standard SQL requires that even a query must start a new transaction if there is no transaction currently in progress. There are DBMS where that is not what … Read more
It’s really late, and I only spent about 10 minutes on this, so its extremely sloppy, however it does work and will give you a good jumping off point: using System; using System.Collections.Generic; using System.Text; using System.Reflection; namespace TableGenerator { class Program { static void Main(string[] args) { List<TableClass> tables = new List<TableClass>(); // Pass … Read more
Both input and output parameters can be assigned defaults. In this example: CREATE PROCEDURE MyTest @Data1 int ,@Data2 int = 0 ,@Data3 int = null output AS PRINT @Data1 PRINT @Data2 PRINT isnull(@Data3, -1) SET @Data3 = @Data3 + 1 RETURN 0 the first paramter is required, and the second and third are optional–if not … Read more
Since you need to perform multiple inserts, database will be hit multiple times. The delay in your case is because each save is done in different DB transactions. You can reduce the latency by enclosing all your operations in one transaction. class Foo belongs_to :parent, :class_name => “Foo” has_many :children, :class_name => “Foo”, :foreign_key=> “parent_id” … Read more