Shibboleth Developers

[Chad La Joie <>]

Well, with SQL, you get multiple results but each result has the same 
same data columns.  With JNDI that need not be the case.  The same query 
that gives you people could give you groups, computer accounts, etc., 
each with totally different data schemas.  I worry that loosing that 
sort of contextual information and just mashing stuff together might 
lead to confusing results for people.

Scott Cantor wrote:
> > JNDI, not JDBC.  This isn't an issue with the database stuff.
>
>
> But what's the difference? If this is the same issue (not sure, but it
> sounds similar), why wouldn't we just move the JDBC code that configures the
> min/max values up the hierarchy, and then implement the restrictions in the
> result set processing in the two connectors.
>
> The only reason I did it that way in the first place is that I didn't have
> experience with or examples of JNDI databases to test with.
>
> -- Scott

--
Chad La Joie             315Q St. Mary's Hall
Project Sentinel         202.687.0124