Misc doc fixes
This commit is contained in:
parent
715f4a748b
commit
144d88fc8b
2 changed files with 3 additions and 3 deletions
4
FU/Pg.pm
4
FU/Pg.pm
|
|
@ -71,7 +71,7 @@ C<$string> can either be in key=value format or a URI, refer to L<the
|
|||
PostgreSQL
|
||||
documentation|https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING>
|
||||
for the full list of supported formats and options. You may also pass an empty
|
||||
string and leave the configuration up L<environment
|
||||
string and leave the configuration up to L<environment
|
||||
variables|https://www.postgresql.org/docs/current/libpq-envars.html>.
|
||||
|
||||
=item $conn->server_version
|
||||
|
|
@ -702,7 +702,7 @@ While C<null> is a valid JSON value, there's currently no way to distinguish
|
|||
that from SQL C<NULL>. When sending C<undef> as bind parameter, it is sent as
|
||||
SQL C<NULL>.
|
||||
|
||||
If you prefer to work with JSON are raw text values instead, use:
|
||||
If you prefer to work with JSON as raw text values instead, use:
|
||||
|
||||
$conn->set_type(json => 'text');
|
||||
|
||||
|
|
|
|||
|
|
@ -121,7 +121,7 @@ FU::SQL - Small and Safe SQL Query Builder
|
|||
|
||||
my $sel = SQL 'SELECT id, name FROM table', WHERE { id => IN([1,2,3]) };
|
||||
|
||||
my($sql, @params) = $sel->compile;
|
||||
my($sql, $params) = $sel->compile;
|
||||
|
||||
=head1 DESCRIPTION
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue