On Nov 23, 2008, at 9:42 PM, Paul McNett wrote:
> You are proving my point.
>
> With SQLite, the connection name becomes the database name. You get
> one database per
> connection. With other databases, you get a connection that can have
> several databases.
Actually, I don't think you are understanding my point.
A connection is to a server, not to a database. With a server like
MySQL, passing the database in the connect string is a shortcut for
connecting to the server and then setting the db as the current
namespace. While this gets muddy with file-based backends, the
"server" in this case is the file. The problem with SQLite is that
it's creating *servers* on the fly, not databases.
I have this on my to-do list for tonight. Preventing file creation is
easy; I have to now find all the UI hooks that need to catch that
error and relay it to the user.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
