dovecot - Sep 2011 - Problem with configuring dovecot to take namespaces from database

Hello!
I'd like to set up dovecot to keep namespaces in database, keep more 
than one namespace per user.

I try to create the simplest rule (even without tuple in db table) to 
get new namespace, unfortunately it doesn't work.

My user_query is:
SELECT '/dane/domeny/%d/mail/%n/' as home, dovecot_typ_skrzynki
||':'||
'/dane/domeny/%d/mail/%n/' ||'.'|| dovecot_typ_skrzynki as 
mail_location, '*:bytes='||quota_mb||'M' as quota_rule , 
'test33/location=mdbox:~/.mdbox/test33/' as
"namespace/test3/prefix"

In debug log i'm getting:
Debug: master out: 
USER#0111#011user at
examle.com#011home=/dane/domeny/mejor.pl/mail/marcin/#011mail_location=maildir:/dane/domeny/mejor.pl/mail/marcin/.maildir#011quota_rule=*:bytes=0M#011namespace/test3/prefix=test33/location=mdbox:~/.mdbox/test33/

If i knew how it should look like the line in auth debug log for working 
configuration it could be easier for me to write correct sql query.
May i please for advice?

dovecot -n output (with version number)?

On 7.9.2011, at 17.42, Marcin Miros?aw wrote:
> Hello!
> I'd like to set up dovecot to keep namespaces in database, keep more
than one namespace per user.
> 
> I try to create the simplest rule (even without tuple in db table) to get
new namespace, unfortunately it doesn't work.
> 
> My user_query is:
> SELECT '/dane/domeny/%d/mail/%n/' as home, dovecot_typ_skrzynki
||':'|| '/dane/domeny/%d/mail/%n/' ||'.'||
dovecot_typ_skrzynki as mail_location, '*:bytes='||quota_mb||'M'
as quota_rule , 'test33/location=mdbox:~/.mdbox/test33/' as
"namespace/test3/prefix"
> 
> In debug log i'm getting:
> Debug: master out: USER#0111#011user at
examle.com#011home=/dane/domeny/mejor.pl/mail/marcin/#011mail_location=maildir:/dane/domeny/mejor.pl/mail/marcin/.maildir#011quota_rule=*:bytes=0M#011namespace/test3/prefix=test33/location=mdbox:~/.mdbox/test33/
> 
> If i knew how it should look like the line in auth debug log for working
configuration it could be easier for me to write correct sql query.
> May i please for advice?
>