just use the scalar version:
for
Value: ( 'update' | 'shared' | \$scalar )
Set to 'update' for a SELECT ... FOR UPDATE or 'shared' for a SELECT
... FOR SHARED. If \$scalar is passed, this is taken directly and
embedded in the query.
with
```
{
for => \q{UPDATE SKIP LOCKED}
}
```
On 4 May 2016, at 12:59, Dmitry Belyavsky wrote:
> Hello,
>
> is there a support for the PostgreSQL SELECT FOR UPDATE SKIP LOCKED clause
> in the DBIx::Class? And how difficult is to add it if not?
>
> Thank you!
>
>
> --
> SY, Dmitry Belyavsky
> _______________________________________________
> List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
> IRC: irc.perl.org#dbix-class
> SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
> Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
signature.asc
Description: OpenPGP digital signature
_______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
