or you could have the common settings loaded by a 'require' as the first line of your hook and have a sub in an arbitrary namespace (e.g. RadiatorDBI::) in a closure that returns the dbh if its ->ping method works or creates a new one otherwise ...
There might be something you could do with the Radiator DB modules as well, but they seem a trifle clunky for my taste so if I were needing that sort of stuff I'd probably use Ima::DBI > -----Original Message----- > From: John McFadden [mailto:[EMAIL PROTECTED] > Sent: 09 July 2003 16:47 > To: [EMAIL PROTECTED] > Subject: (RADIATOR) Use of Oracle in PostAuthHook? > > > We use LDAP to do the basic userid/password authentication > but intend to > use one or more Oracle databases > to apply business rules as LDAP is not dynamic enough. > > The PostAuthHook gives us a place to do that but I'm not sure if I > should try to do it within Radiator or > via an external program call. > > I'm a bit nervious about the Radiator/Perl SQL overhead. > > Does the PostAuthHook require a new connection for each > request or for > each session or each user? > Or can I open the connection in a StartupHook (global var) then just > share it in the PostAuthHook to do the required SQL query. > Since we're just doing queries I'm hoping to share one connection to > minimize overhead. Any issues with concurrency if we do? > > How do I detect the database is down and attempt to allocate a new > connection? > > Comments, suggestions? > > Regards JLM > > > > > > > > > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
