Static DataTable or DataSet in a class – bad idea?

I have several instances of a class. Each instance stores data in a common database. So, I thought “I’ll make the DataTable table field static, that way every instance can just add/modify rows to its own table field, but all the data will actually be in one place!”

Why does this static field always get initialized over-eagerly?

I am looking at this excellent article from Jon Skeet.

In memory collection vs database vs individual classes for infrequently changed objects

I have a ASP.NET application which puts the users through a series of forms in a wizard like fashion and has them fill out fields on the form. In code, these forms and fields are represented as “Step” objects, with a collection of “Field” objects as properties.

Is there a name for this design pattern? [closed]

Closed 10 years ago.

Best practice for creating a ‘global’ config class used by numerous components

I have a large project with a driver part and about 5 libraries doing various associated tasks. Many of the libraries require access to ‘global’ configuration data which is read from a database at startup by the driver code. By driver I just mean the part which contains the main function.

Storing session in a static variable?

I’m currently checking a older piece of C# code used to maintain a login session.

Issues about static injection in Spring?

I use spring-boot with spring xml in my project.
I wrapper the DAOs in a DataAccessService class to serve as a DB service layer, both the service and the DAOs are injected in spring xml and used by Autowired.

Applying initialization-on-demand holder idiom at variable level rather than class

I was looking for the idiomatic way to implement thread-safe lazy initialization for a configuration collection retrieved from the DB inside a Spring bean.

Is static going to make any difference in this code snippet

I have been to an interview and was asked this question – is there any difference adding or removing the static keyword in these classes?

Will this singleton style class work with accessing a session on multiple MVC controllers?

Question background: