Alex Hudson escribió: >> What will be the result of this BQL ? >> >> |! nmap.type 9999| >> > > This would just turn into a where clause, WHERE so.type != 9999, > ignoring the | characters. >
The | characters was a mistake. Copy+Paste... Sorry.. :-( > I think the root of your question, though, is "Can I set up BQL > statements which are potentially dangerous in some way?". I hope the > answer to this is roughly, "no". > That was the answer to the first part of the question. The second one is if we have any way to restrict the access to a client to _only_ a subselect of the whole mail system. In example: Client X can only access to items.type 2. No access to the others.. Or Client Z can only access to all items but not on a particular domain '[EMAIL PROTECTED]'. I mean a better granularity security when a client is accessing to the mail system and NOT whole access to whole clients. I hope I had explained my question a bit better. > .... However, anyone running BQL against the store has to be > authenticated anyway,..... Ok.... perhaps this answer the second part of my question... Greetings.... _______________________________________________ Bongo-devel mailing list [email protected] https://mail.gna.org/listinfo/bongo-devel
