@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.11\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2022-11-13 04:34 +0000\n "
15+ "POT-Creation-Date : 2022-11-25 16:25 +0000\n "
1616"PO-Revision-Date : 2021-06-28 01:13+0000\n "
1717"Last-Translator : Maciej Olko <maciej.olko@gmail.com>, 2022\n "
1818"Language-Team : Polish (https://www.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -208,6 +208,9 @@ msgstr ""
208208msgid ":ref:`sqlite3-connection-context-manager`"
209209msgstr ""
210210
211+ msgid ":ref:`sqlite3-howto-row-factory`"
212+ msgstr ""
213+
211214msgid ""
212215":ref:`sqlite3-explanation` for in-depth background on transaction control."
213216msgstr ""
@@ -999,18 +1002,14 @@ msgid ""
9991002msgstr ""
10001003
10011004msgid ""
1002- "A callable that accepts two arguments, a :class:`Cursor` object and the raw "
1003- "row results as a :class:`tuple`, and returns a custom object representing an "
1004- "SQLite row."
1005+ "The initial :attr:`~Cursor.row_factory` for :class:`Cursor` objects created "
1006+ "from this connection. Assigning to this attribute does not affect the :attr:"
1007+ "`!row_factory` of existing cursors belonging to this connection, only new "
1008+ "ones. Is ``None`` by default, meaning each row is returned as a :class:"
1009+ "`tuple`."
10051010msgstr ""
10061011
1007- msgid ""
1008- "If returning a tuple doesn't suffice and you want name-based access to "
1009- "columns, you should consider setting :attr:`row_factory` to the highly "
1010- "optimized :class:`sqlite3.Row` type. :class:`Row` provides both index-based "
1011- "and case-insensitive name-based access to columns with almost no memory "
1012- "overhead. It will probably be better than your own custom dictionary-based "
1013- "approach or even a db_row based solution."
1012+ msgid "See :ref:`sqlite3-howto-row-factory` for more details."
10141013msgstr ""
10151014
10161015msgid ""
@@ -1083,9 +1082,9 @@ msgid "*sql_script* must be a :class:`string <str>`."
10831082msgstr ""
10841083
10851084msgid ""
1086- "If :attr:`~Connection .row_factory` is ``None``, return the next row query "
1087- "result set as a :class:`tuple`. Else, pass it to the row factory and return "
1088- "its result. Return ``None`` if no more data is available."
1085+ "If :attr:`~Cursor .row_factory` is ``None``, return the next row query result "
1086+ "set as a :class:`tuple`. Else, pass it to the row factory and return its "
1087+ "result. Return ``None`` if no more data is available."
10891088msgstr ""
10901089
10911090msgid ""
@@ -1170,6 +1169,20 @@ msgid ""
11701169"methods."
11711170msgstr ""
11721171
1172+ msgid ""
1173+ "Control how a row fetched from this :class:`!Cursor` is represented. If "
1174+ "``None``, a row is represented as a :class:`tuple`. Can be set to the "
1175+ "included :class:`sqlite3.Row`; or a :term:`callable` that accepts two "
1176+ "arguments, a :class:`Cursor` object and the :class:`!tuple` of row values, "
1177+ "and returns a custom object representing an SQLite row."
1178+ msgstr ""
1179+
1180+ msgid ""
1181+ "Defaults to what :attr:`Connection.row_factory` was set to when the :class:`!"
1182+ "Cursor` was created. Assigning to this attribute does not affect :attr:"
1183+ "`Connection.row_factory` of the parent connection."
1184+ msgstr ""
1185+
11731186msgid "Row objects"
11741187msgstr ""
11751188
@@ -1180,7 +1193,9 @@ msgid ""
11801193"index."
11811194msgstr ""
11821195
1183- msgid "Two row objects compare equal if have equal columns and equal members."
1196+ msgid ""
1197+ "Two :class:`!Row` objects compare equal if they have identical column names "
1198+ "and values."
11841199msgstr ""
11851200
11861201msgid ""
@@ -1607,6 +1622,53 @@ msgid ""
16071622"found in the `SQLite URI documentation`_."
16081623msgstr ""
16091624
1625+ msgid "How to create and use row factories"
1626+ msgstr ""
1627+
1628+ msgid ""
1629+ "By default, :mod:`!sqlite3` represents each row as a :class:`tuple`. If a :"
1630+ "class:`!tuple` does not suit your needs, you can use the :class:`sqlite3."
1631+ "Row` class or a custom :attr:`~Cursor.row_factory`."
1632+ msgstr ""
1633+
1634+ msgid ""
1635+ "While :attr:`!row_factory` exists as an attribute both on the :class:"
1636+ "`Cursor` and the :class:`Connection`, it is recommended to set :class:"
1637+ "`Connection.row_factory`, so all cursors created from the connection will "
1638+ "use the same row factory."
1639+ msgstr ""
1640+
1641+ msgid ""
1642+ ":class:`!Row` provides indexed and case-insensitive named access to columns, "
1643+ "with minimal memory overhead and performance impact over a :class:`!tuple`. "
1644+ "To use :class:`!Row` as a row factory, assign it to the :attr:`!row_factory` "
1645+ "attribute:"
1646+ msgstr ""
1647+
1648+ msgid "Queries now return :class:`!Row` objects:"
1649+ msgstr ""
1650+
1651+ msgid ""
1652+ "You can create a custom :attr:`~Cursor.row_factory` that returns each row as "
1653+ "a :class:`dict`, with column names mapped to values:"
1654+ msgstr ""
1655+
1656+ msgid ""
1657+ "Using it, queries now return a :class:`!dict` instead of a :class:`!tuple`:"
1658+ msgstr ""
1659+
1660+ msgid "The following row factory returns a :term:`named tuple`:"
1661+ msgstr ""
1662+
1663+ msgid ":func:`!namedtuple_factory` can be used as follows:"
1664+ msgstr ""
1665+
1666+ msgid ""
1667+ "With some adjustments, the above recipe can be adapted to use a :class:"
1668+ "`~dataclasses.dataclass`, or any other custom class, instead of a :class:"
1669+ "`~collections.namedtuple`."
1670+ msgstr ""
1671+
16101672msgid "Explanation"
16111673msgstr "Wytłumaczenie"
16121674
0 commit comments