dbconnection

Which of the following two is more accurate? select numbackends from pg_stat_database; select count(*) from pg_stat_activity; Magnus Hagander Those two requires aren't equivalent. The equivalent version of the first one would be: SELECT sum(numbackends) FROM pg_stat_database; In that case, I would expect that version to be slightly faster than the second one, simply because it has fewer rows to count. But you are not likely going to be able to measure a difference. Both queries are based on exactly the same data, so they will be equally accurate. The following query is very helpful select *

I'm trying to unit test a few .NET classes that (for good design reasons) require DbConnections to do their work. For these tests, I have certain data in memory to give as input to these classes. That in-memory data could be easily expressed as a DataTable (or a DataSet that contains that DataTable), but if another class were more appropriate I could use it. If I were somehow magically able to get a DbConnection that represented a connection to the in-memory data, then I could construct my objects, have them execute their queries against the in-memory data, and ensure that their output matched

I have the following connection string: Data Source=Paul-HP\MYDB;Initial Catalog=MyMSDBSQL;Persist Security Info=True;User ID=sa;Password=password (.net webservice) This can obviously be viewed simply by opening up the app.config file and looking at the configuration settings. What I need is a way to make a hacker unable to see the password. But at the same time, leave it customisable so that it can be changed when deployed on another database. You have a number of options - the ones that I am aware of (in order of preference): Use integrated (SSPI) security where you don't need to include a

To rephrase the question: should I avoid sharing instances of classes which implement java.sql.Connection between different threads? skaffman If the JDBC driver is spec-compliant, then technically yes, the object is thread-safe, but you should avoid sharing connections between threads, since the activity on the connection will mean that only one thread will be able to do anything at a time. You should use a connection pool (like Apache Commons DBCP ) to ensure that each thread gets its own connection. java.sql.Connection is an interface. So, it all depends on the driver's implementation, but