shibboleth-dev - RE: Bug 308: Exception thrown on multi-results with JNDI connector

Subject: Shibboleth Developers

List archive

RE: Bug 308: Exception thrown on multi-results with JNDI connector

From: "Scott Cantor" <>
To: "'Chad La Joie'" <>, <>
Subject: RE: Bug 308: Exception thrown on multi-results with JNDI connector
Date: Tue, 17 May 2005 20:31:55 -0400
Organization: The Ohio State University

> Does this sound reasonable?

Maybe I'm not following the bug, but there's already code in the JDBC
connector to indicate the acceptable min and max rows to consider "legal"
from the connector. So if you have a query that is known to return multiple
rows, you can allow that, or force a maximum of one, or force at least one
to prevent nulls, etc.

Isn't that more general? We could just promote that code up the class
hierarchy...

-- Scott

Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
- RE: Bug 308: Exception thrown on multi-results with JNDI connector, Scott Cantor, 05/17/2005
  - Re: Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
    - RE: Bug 308: Exception thrown on multi-results with JNDI connector, Scott Cantor, 05/17/2005
      - Re: Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
        
        RE: Bug 308: Exception thrown on multi-results with JNDI connector, Scott Cantor, 05/17/2005
        
        Re: Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
- Re: Bug 308: Exception thrown on multi-results with JNDI connector, Walter Hoehn, 05/17/2005

List archive

RE: Bug 308: Exception thrown on multi-results with JNDI connector