Skip to content
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.

Support optional parameters in routes #152

Open
dantleech opened this issue Feb 8, 2015 · 3 comments
Open

Support optional parameters in routes #152

dantleech opened this issue Feb 8, 2015 · 3 comments

Comments

@dantleech
Copy link
Member

It should be possbile to have auto generated routes with optional parameters:

e.g.

/articles/page/{page}

Where page is a parameter to be passed to the controller.

@dantleech
Copy link
Member Author

@petforsberg is that accurate?

@petforsberg
Copy link

Sorry for a delay, yes sure, this was what I meant. :)

BTW, considering paginator etc. and performance: do you know about the performance impact when two PHPCR-ODM queries are considered:

  1. get ALL records (nodes) from the given repository / class
  2. get limited number of records (let's say 10 or so)

I'm asking of it, because implementations of paginators usually expect whole collection, which is then stripped to a given number. (It's easier to always get all records, and then limit data, than having multiple versions of a query, but the performance is prio).

@dantleech
Copy link
Member Author

Getting a limited number of records would be faster I would think, but better to benchmark yourself. Please continue this discussion in a Doctrine PHPCR-ODM issue https://github.com/doctrine/phpcr-odm as this is off topic here :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants