>Speaking to the OP: personally, I don't like the approach of putting data
>access methods at the module level to >begin with. I'd rather use a class.
>Just because it makes sense to have a singleton connection now doesn't mean it
>>will always make sense as your application grows.
>In fact,
On Thu, Aug 1, 2013 at 6:49 PM, Dennis Lee Bieber wrote:
> On Thu, 1 Aug 2013 15:05:08 +, "Joseph L. Casale"
> declaimed the following:
>
>>
>>As the module opens a connection, wherever I import it I call a commit against
>>the connection after invoking any methods that insert or change data.
On 2013-08-01, Joseph L. Casale wrote:
> A bit vague I know, but does anyone see the obvious mistake? I
> assumed the module setting up a singleton connection was a
> perfectly viable way to accomplish this?
My one db application started out creating a new connection to
the db (sqlite3) for every
