Throw Vs Throw ex Posted: 29 Jun 2010 08:41 AM PDT Throw Throw Ex try { // do some operation that can fail } catch (Exception ex) { // do some local cleanup throw ; } try { // do some operation that can fail } catch (Exception ex) { // do some local cleanup throw ex; } It preserve the Stack information with Exception It Won't Send Stack information with Exception This is called as "Rethrow" This is called as "Breaking the Sta...
There are three basic classifications of patterns Creational, Structural, and Behavioral patterns. Creational Patterns • Abstract Factory :- Creates an instance of several families of classes • Builder : - Separates object construction from its representation • Factory Method :- Creates an instance of several derived classes • Prototype :- A fully initialized instance to be copied or cloned • Singleton :- A class in which only a single instance can exist Note : - The best way to remember Creational pattern is by remembering ABFPS (Abraham Became First President of States). Structural Patterns • Adapter :-Match interfaces of different classes . • Bridge :-Separates an object’s abstraction from its implementation. • Composite :-A tree structure of simple and composite objects. • Decorator :-Add responsibilities to objects dynamically. • Façade :-A single class that represents an entire subsystem. • Flyweight :-A fine-grained instance used for efficient sharing...
Relational databases like SQL Server use indexes to find data quickly when a query is processed. Creating and removing indexes from a database schema will rarely result in changes to an application's code; indexes operate 'behind the scenes' in support of the database engine. However, creating the proper index can drastically increase the performance of an application. The SQL Server engine uses an index in much the same way a reader uses a book index. For example, one way to find all references to INSERT statements in a SQL book would be to begin on page one and scan each page of the book. We could mark each time we find the word INSERT until we reach the end of the book. This approach is pretty time consuming and laborious. Alternately, we can also use the index in the back of the book to find a page number for each occurrence of the INSERT statements. This approach produces the same results as above, but with tremendous savings in time. When a SQL Server has ...
Comments
Post a Comment