When using @group keyword, grouping is not peformed,
and items are shown in no particular order. 

sort and sortrev methods of metakit PyView object,
expect sequences of Property objects, like here:

sorted = view.sortrev((view.assignedto,), (view.name,)).

Roundup back_metakit.py, supplies lists of strings:

sorted = view.sortrev([ 'assignedto', ], [ 'name' ]);

which is interpreted improperly.

The attached file demonstrates a simple session log
with metakit database, demonstrating this issue with
view.sortrev behaviour.

I found no references in mk4py that sortrev accepts
sequences of strings as arguments, so I consider this
to be back_metakit.py bug.

Logged In: YES 
user_id=714555

Sorry, wrong alarm. Anyway, the grouping is broken, but
sortrev arguments is ok.

I have two classes: order(id, name, assignedto, ...),
group(id, name, ...), and the 'name' attribute seems to
confuse back_metakit.py.

Logged In: YES 
user_id=714555

The metakit backend was confused by overlapping column
names. I changed the schema, and the bug has gone.

Logged In: YES 
user_id=6405

Sorry, I'm not sure that I understand. Could you clarify whether or not 
there is a bug in the metakit backend? 

Logged In: YES 
user_id=714555

I had two classes:
gr=Class(db, "group", name = String(),
members=Multilink("user"))
gr.setkey("name")
Class(db, "order", name = String(), assignedto = Link("order"))

I developed it with back_bsddb3, and grouping on
"assignedto" property worked fine
("...&@group=assignedto..."). Then I switched roundup
instance to back_metakit, and grouping stopped working.

back_metakit seems to sort (since grouping in back_metakit
is done with sorting) items on "name" property.

If having two same properties in different linked classes,
then it's a bug. Otherwise it's not.