Poo-tee-weet

XPath expert needed

Lukas Kahwe Smith — Fri, 24 May 2013 20:27:07 +0200

In the PHPCR implementation using Doctrine DBAL we support search queries by converting the SQL2/QOM statements into XPath queries that we run on the XML stored in an RDBMS. Sounds insane, yes .. but it works pretty well .. obviously will not scale very well .. but it works for smaller data sets and there will be ways to improve performance later. In terms of functionality we have everything working quite well including JOIN support that was added recently.

However we are stuck with multivalue queries. What makes it particularly tricky is that we do not know which properties are multivalue and which are not as illustrated by these tests.

As you can see in the test we have a multivalue property "tags" and in the SQL2 statement we want to test if that multivalue property contains both "foo" and "bar". However inside the query engine we do not know that this property is multivalued or not.

The relevant code is in QOMWalker:: sqlXpathValueExists() and QOMWalker:: sqlXpathExtractValue(). As you can see it currently only looks at "sv:value[1]".

You can find some more information here:
https://github.com/jackalope/jackalope-doctrine-dbal/issues/88

Re: What is needed to REST in Symfony2

Sat, 18 May 2013 07:41:52 +0200

It seems to me that no one really gets into resource linking. In some apps, I've created a custom form type for giving the ability to just simply pass in an id as you would a hidden form type in common forms.

There are SOO many standards on linking.

The link you posted earlier (http://jsonapi.org) has a clever way of doing it (I'm much more in favor of just having simple ids).

For example... You have a resource at GET /api/user

{
id: 1,
name: "Jordan",
links: {
best_friend: 1
}
}

And if you want to change his best friend... PATCH /api/user/1

[
{ "op": "replace", "path": "/links/author", "value": 2 }
]

Nothing allows for this yet... but this is pretty ugly in itself and no javascript frameworks work with this yet out of the box, so an alternative would be:

PATCH /api/user/1
{

best_friend: 2
}

There's just no clear way of doing it :(

Re: What is needed to REST in Symfony2

fieg — Sat, 11 May 2013 18:03:53 +0200

2) Dynamic content in NelmioApiDocBundle and/or some way to integrate with JMSSerializer exclusion strategies (f.e. so that I can version my API docs together with my API)

About the exclusion strategies, that feature is almost done. Checkout the PR here: https://github.com/nelmio/NelmioApiDocBundle/pull/156

Re: What is needed to REST in Symfony2

weaverryan — Fri, 10 May 2013 03:39:31 +0200

In addition to everything you've said, I'd like to add another: documentation / tutorial. A tutorial on FOSRestBundle - which of course more broadly means that people want to know about REST - is the most asked-for tutorial at KnpUniversity.com (https://knpuniversity.uservoice.com/forums/143666-how-can-we-improve-knpuniversity-/filters/top) . But even for me, I find using all of these tools together in advanced cases very difficult, which means that no tutorial has been created yet. They're individually great, but still a bit low-level, and finding best practices and a full-view of using everything together seems to still be missing.

@lsmith If we made a tutorial on REST in Symfony2, would you also donate your expertise to make sure it's done well? And if not you, who? Our new screencasts all have open source scripts, (even if the video is paid), so anyone can benefit. With a little bit of tech help, we'll run the rest of the way with this :). And really, that goes for a lot of topics... ;)

Cheers!

Re: What is needed to REST in Symfony2

Lukas Kahwe Smith — Tue, 07 May 2013 09:08:57 +0200

Another topic we maybe should look into http://jsonapi.org