Basically, the current unit tests do not require a connection to the db. There needs to be a way to set the adapter to use without having a connection. The code surrounding this is still a bit messy. But you can see in the CriteriaTest how I test a couple of the adapter variations.
john mcnally On Mon, 2002-06-03 at 16:16, Daniel Rall wrote: > Bill Schneider <[EMAIL PROTECTED]> writes: > > > Exactly--if you can determine your database vendor at runtime, you can point > > your app server's datasource definition at a different database without > > having to touch Torque.properties. > > > > I was thinking of having the initialization routine somewhere determine the > > db adapter type for each datasource that doesn't have an explicit adapter > > property. > > > > How would it complicate unit tests? > > Try it and find out. ;-) > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
