On Dec 10, 2007, at 3:30 PM, Mike McGonagle wrote:
On 12/10/07, Mathieu Bouchard matju@artengine.ca wrote: But it requires multiple logins, perhaps many at once, which might be wasteful. For sharing database connections between several [psql] objects, what do you think would be the best ways to do it? This is supposing that several different database connections can still be used at once, as specified in the patches.
In one of the early prototypes I wrote for this, I set it up so
that the connections were shared. Basically, when an object tried
to open a connection, it would check if there was already one open,
and if so, it would use that. Else it would create a new
connection, which would then get stored in the global connection
object.One thing that I would be curious about would be any collisions in
using a shared object, but I also think that should be something
left to think about in building the PD patch.
It is useful to represent the pieces in Pd space, so you can
understand what's going on. That's one reason why I advocate having
the core object represent the connection to the database rather than
a query. Otherwise, it's starts to become more like Max/MSP's mega-
objects (coll, zl, etc) that are really like mini-applications than
programming.
There still can be query objects, they would just be designed to feed
to the core database objects. These query objects would then be
usable if we maintain the same interface.
.hc
News is what people want to keep hidden and everything else is
publicity. - Bill Moyers