Getting All Properties Std. and Custom

Hi Miguel,
  Yes you got my point, what i need. You have given me
suggestion. Can you little more explain on your idea , how
to do that.

Miguel Figueiredo <mfigueiredomaisis.pt> wrote:
  
Hello Marco, Aslam,

Don't know how I missed Julian's remark on availability of
this kind of
query, so cut out the first part of my previous message,
leaving only second
part, witch would still work although it kind of creepy
(accessing Slide's
meta information DB directly).

Anyway, concerning Marco question transcribed below. From
what I
understood, Aslam wants to know, with one request, every
custom property
defined in the repository. He would next populate a list
with it, so users
could use the same property instead of creating new similar
ones. Means that
the request should be done globally in the repository, and
that's thousands
of documents. Because the query must be done globally, I
would not advise to
make a query for every resource in the repository and then
filter down on
client side (even client side): just imagine matching 100
000 documents,
building a DASL result of it (xml), and then parse it.

Aslam, you could do it easily if you managed the possible
property list
outside Slide (keeping a property name list in a
configuration file or DB,
and then retrieve that information instead of querying
Slide).

Hope this helps,
Miguel Figueiredo

-----Original Message-----
From: Marco Ferretti [mailto:marco.ferrettifermasoft.com] 
Sent: quarta-feira, 6 de Setembro de 2006 5:55
To: Slide Users Mailing List
Subject: Re: Getting All Properties Std. and Custom

On Wednesday 06 September 2006 05:23, aslam bari wrote:
> Ok ,
> First of all it is not possible in my program. Because
in my program a
> user can make a property in only one custom namespace
which is defined by
> my program and hide from user. So now there are only
two namespace DAV:
and
> my custom namespace. So, Now i can get standard DAV:
properties of a
> resource which are not more than 15-16. But what about
custom namespace
> properties because i don't know on which resource and
by what name and how
> many properties a user has given. Help Plz.
>
Hi Aslam ,

as Julian already told you, it is not possible to create a
query that
filters 
by namespace. What you have to do is filter your data
"manually" after the 
DASL query's been performed.

Actually, apart from the possibility to create a query that
filters your
data 
server side ( and which we discovered not being possible) ,
I don't see ( = 
understand ) why you need to know the number of custom
properties for each 
resource BEFORE parsing the result of the DASL query.

ciao

Marco

-- 
You are capable of planning your future.


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org



 				
---------------------------------
 Here's a new way to find what you're looking for - Yahoo!
Answers 
 Send FREE SMS to your friend's mobile from Yahoo!
Messenger Version 8. Get it NOW

Hello Aslam,

 If you're asking about the last remark, it's just a
simple workaround for a
property list management. As an example, you could use this
solution: create
a DB table with a OID and string called PROPERTY_NAME. Then
use your
favourite O/RM tool to access the database table and allow
you to read and
write into it. When you need to find all defined custom
properties, just
list the contents of that table.
 Another way to do this, witch I called creepy (you have to
figure out how
the persistence model works) in the last mail, was to access
slide database
tables, and query them for distinct property names.

Hope this helps,
Miguel Figueiredo

-----Original Message-----
From: aslam bari [mailto:iamaslamokyahoo.co.in] 
Sent: quinta-feira, 7 de Setembro de 2006 4:46
To: Slide Users Mailing List
Subject: RE: Getting All Properties Std. and Custom

Hi Miguel,
  Yes you got my point, what i need. You have given me
suggestion. Can you
little more explain on your idea , how to do that.

Miguel Figueiredo <mfigueiredomaisis.pt> wrote:
  
Hello Marco, Aslam,

Don't know how I missed Julian's remark on availability of
this kind of
query, so cut out the first part of my previous message,
leaving only second
part, witch would still work although it kind of creepy
(accessing Slide's
meta information DB directly).

Anyway, concerning Marco question transcribed below. From
what I
understood, Aslam wants to know, with one request, every
custom property
defined in the repository. He would next populate a list
with it, so users
could use the same property instead of creating new similar
ones. Means that
the request should be done globally in the repository, and
that's thousands
of documents. Because the query must be done globally, I
would not advise to
make a query for every resource in the repository and then
filter down on
client side (even client side): just imagine matching 100
000 documents,
building a DASL result of it (xml), and then parse it.

Aslam, you could do it easily if you managed the possible
property list
outside Slide (keeping a property name list in a
configuration file or DB,
and then retrieve that information instead of querying
Slide).

Hope this helps,
Miguel Figueiredo

-----Original Message-----
From: Marco Ferretti [mailto:marco.ferrettifermasoft.com] 
Sent: quarta-feira, 6 de Setembro de 2006 5:55
To: Slide Users Mailing List
Subject: Re: Getting All Properties Std. and Custom

On Wednesday 06 September 2006 05:23, aslam bari wrote:
> Ok ,
> First of all it is not possible in my program. Because
in my program a
> user can make a property in only one custom namespace
which is defined by
> my program and hide from user. So now there are only
two namespace DAV:
and
> my custom namespace. So, Now i can get standard DAV:
properties of a
> resource which are not more than 15-16. But what about
custom namespace
> properties because i don't know on which resource and
by what name and how
> many properties a user has given. Help Plz.
>
Hi Aslam ,

as Julian already told you, it is not possible to create a
query that
filters 
by namespace. What you have to do is filter your data
"manually" after the 
DASL query's been performed.

Actually, apart from the possibility to create a query that
filters your
data 
server side ( and which we discovered not being possible) ,
I don't see ( = 
understand ) why you need to know the number of custom
properties for each 
resource BEFORE parsing the result of the DASL query.

ciao

Marco

-- 
You are capable of planning your future.


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org



 				
---------------------------------
 Here's a new way to find what you're looking for - Yahoo!
Answers 
 Send FREE SMS to your friend's mobile from Yahoo!
Messenger Version 8. Get
it NOW


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org