Menu
Community /Pin to ProfileBookmark
@NogDogJan 05.2010 — #While I will not say to never use singletons, before using them, you should read the arguments against it: http://www.google.com/search?q=why+singletons+are+evil
Personally, I tend to create a single database object (usually based on or extending the MySQLi or PDO class), and pass it to the constructors of objects which need it. I guess I prefer the visibility that provides in the interface.
If you prefer to invoke it from within each class from a global source, then I suspect a static variable might be a bit more efficient than invoking a singleton object in each class that needs it, but that's only a guess.
advantage?
Is there any advantages of storing database connection in static member variable instead of non static one that is encapsulated in singleton pattern? I just want to make sure that there isn’t any before I implement.
Sign in
to post a comment6 Comments(s) ↴
0
@NogDogJan 05.2010 — #While I will not say to never use singletons, before using them, you should read the arguments against it: Personally, I tend to create a single database object (usually based on or extending the MySQLi or PDO class), and pass it to the constructors of objects which need it. I guess I prefer the visibility that provides in the interface.
If you prefer to invoke it from within each class from a global source, then I suspect a static variable might be a bit more efficient than invoking a singleton object in each class that needs it, but that's only a guess.