If 'fat' is qualified solely by feature, then attribute scoped queries
constrained to a user-definable base don't qualify ... at least by my
definition.  I may, however, qualify 'fat' as a combination of features,
efficiency and usefulness (or the lack thereof on the latter two).

As for the spelling, huh? :-/

--
Dean Wells
MSEtechnology
* Email: [EMAIL PROTECTED]
http://msetechnology.com


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Monday, April 04, 2005 8:31 PM
To: [email protected]
Subject: RE: [ActiveDir] GroupBy type queries in LDAP

Once we have ASQ available for subtree queries effectively creating join
capability we can start to call LDAP fat no matter what the qualifiers
IMO... ;o)

On the J vs j part, are you saying the English can't spell correctly? <eg>

   joe


 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dean Wells
Sent: Monday, April 04, 2005 7:00 PM
To: Send - AD mailing list
Subject: RE: [ActiveDir] GroupBy type queries in LDAP

To add to Joe's response (and I'm English so I'll use a capital 'J' even if
he doesn't :-), DAP fell short on this goal too.  Ironically, like for like,
LDAP is now probably 'fatter' than DAP though, of course, it depends on what
qualifies as fat.

--

Dean Wells
MSEtechnology
* Email: [EMAIL PROTECTED]
http://msetechnology.com


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Monday, April 04, 2005 6:04 PM
To: [email protected]
Subject: RE: [ActiveDir] GroupBy type queries in LDAP

Yep. The first word of LDAP is lightweight for a reason. It isn't intended
to remove the need for heavier/fatter SQL type query languages and DBs. You
could still, however, do this without a SQL Server, it would require a
script or code to output what you want. As Gil indicated, you sort and then
dump the records that have shared attribute values. If you have the server
sort the results when sending them back, the code is pretty easy to output
this.

Personally I would write the script to do it vs putting into SQL Server but
it is very rare that I think the solution is to move the data into SQL
Server. 

  joe

 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gil Kirkpatrick
Sent: Monday, April 04, 2005 5:47 PM
To: [email protected]
Subject: RE: [ActiveDir] GroupBy type queries in LDAP

Can't do that in LDAP... About the best you can do is use the LDAP sort
control to get a list of entries sorted by Attribute1, but that only gets
you halfway to what you want.

I suspect Al's strategy is the best way to go.

-gil 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al
Sent: Monday, April 04, 2005 2:34 PM
To: [email protected]
Subject: RE: [ActiveDir] GroupBy type queries in LDAP

Is it just user objects?  

(&(objectClass=User)(objectCategory=Person)(Attribute1=*)) Would return all
user objects that have a value for Attribute1.  

If you only wanted all user objects where Attribute1 was a duplicate, I
would *think* you have to query based on what's filled in there. i.e.
Attribute1=someduplicatevalue or something similar.  

Might be more productive to bring all of the needed data into a SQL table
and then do your query. LDAP isn't going to do that type of logic that I'm
aware of. 

I'd love to hear differently though :)

Al 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Palenchar
Sent: Monday, April 04, 2005 5:23 PM
To: [email protected]
Subject: [ActiveDir] GroupBy type queries in LDAP

OK, LDAP evangelists,

I need to query our customer-facing AD for a list of all the users who share
a particular attribute. Let's call that attribute "Attribute1."

So, if two people have the same value in Attribute1, I need their DN.

The trick is, that I want the results for all possible values of Attribute1.

In SQL, I would use group by Attribute1 having count(Attribute1) >1 to get a
list of all Attribute1 values where more than one object had the same value.
I would then join that back to the table to get a list of all the DN's with
those values of Attribute1.

Is there a way to do this with an LDAP query.

Please note that the directory contains millions of objects and iterating
through them will be painful.


-Jeremy
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/



List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/



List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to