Mojo::Pg in full Mojolicious applications

[sri]

This seems to have become kind of an FAQ. What is the right way to integrate Mojo::Pg into full Mojolicious applications? And how do we separate concerns properly? When i recently mentioned on IRC that Minion is actually a good example, that caused some confusion, since many folks don't see it as a Model.

So i've tried to make a much more generic example. It is super minimalistic, and its only purpose will be to illustrate what i think a clean Mojolicious application should look like.

    https://github.com/kraih/mojo-pg/commit/45e9d9134e7e7a243099c95ab8bec1b5308fde81

Please let me know if anything is still not clear enough.

--

sebastian

[sri]

Already changed a few things, latest version can always be found in the examples directory.

    https://github.com/kraih/mojo-pg/tree/master/examples/blog

--

sebastian

[sri]

It also occurred to me that we have not yet chosen a default convention for naming CRUD methods in controllers, so here's a proposal.

    package MyApp::Controller::Posts;

    use Mojo::Base 'Mojolicious::Controller';

    # Render a form to create a new post (submitted to "store")

    sub create {...}

    # Delete a post

    sub destroy {...}

    # Render a form to edit a post (submitted to "update")

    sub edit {...}

    # Render a list of posts

    sub index {...}

    # Render a sepcific post

    sub show {...}

    # Store newly created post (submitted by "create")

    sub store {...}

    # Store updated post (submitted by "edit")

    sub update {...}

    1;

--

sebastian

[Joel Berger]

I would propose a different name than than destroy. DESTROY has meaning in Perl and I'd rather not add confusion. Sadly delete does to, so I propose "remove".

[Paul Durden]

I have used remove instead of destroy or delete

On Fri, Mar 13, 2015 at 7:46 AM, Joel Berger <joel.a...@gmail.com> wrote:

I would propose a different name than than destroy. DESTROY has meaning in Perl and I'd rather not add confusion. Sadly delete does to, so I propose "remove".

--
You received this message because you are subscribed to the Google Groups "Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious...@googlegroups.com.
To post to this group, send email to mojol...@googlegroups.com.
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.

[sri]

I would propose a different name than than destroy. DESTROY has meaning in Perl and I'd rather not add confusion. Sadly delete does to, so I propose "remove".

Seems reasonable.

    package MyApp::Controller::Posts;

    use Mojo::Base 'Mojolicious::Controller';

    # Render a form to create a new post (submitted to "store")

    sub create {...}

    # Render a form to edit a post (submitted to "update")

    sub edit {...}

    # Render a list of posts

    sub index {...}

  

    # Remove a post

    sub remove {...}

    # Render a specific post

    sub show {...}

    # Store newly created post (submitted by "create")

    sub store {...}

    # Store updated post (submitted by "edit")

    sub update {...}

    1;

--

sebastian

[sri]

Seems reasonable.

The list has now also made it into a reworked section of the rendering guide.

    https://github.com/kraih/mojo/commit/1febff498fe4a4bca55193f3b8f187b3f8a51ada#diff-5673597847bee81d4615bbe62681edffR798

--

sebastian 

[sri]

The list has now also made it into a reworked section of the rendering guide.

The Mojo::Pg blog example has also been updated with full CRUD.

    https://github.com/kraih/mojo-pg/commit/558fdd9bbb29c5544acc9a89254d1905b712fb07

--

sebastian 

[Eugene Toropov]

I probably miss something but shouldn't every model has access to DB inside it's code with no explicit "pg => shift->pg" argument? Do you suggest passing pg handler to every model as an additional parameter? Doesn't it look weird? I'm asking because I have the same issue with application structure now (relatively new to Mojo). It seems to me there must DB package which one can use where they need and find dbh singleton there. Looking forward to your thoughts on it.

Cheers

Eugene