Units API.

See the Weblate's Web API documentation for detailed description of the API.

GET /api/units/13184011/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://l10n.opensuse.org/api/translations/packages-i18n/perl-master/ja/?format=api",
    "source": [
        "This is a simple module which tries to split any SQL code, even including non-standard extensions (for the details see the SUPPORTED DBMSs section below), into the atomic statements it is composed of.\n\nThe logic used to split the SQL code is more sophisticated than a raw 'split' on the ';' (semicolon) character: first, various different statement terminator _tokens_ are recognized (see below for the list), then this module is able to correctly handle the presence of said tokens inside identifiers, values, comments, 'BEGIN ... END' blocks (even nested), _dollar-quoted_ strings, MySQL custom 'DELIMITER's, procedural code etc., as (partially) exemplified in the SYNOPSIS above.\n\nConsider however that this is by no means a validating parser (technically speaking, it's just a _context-sensitive tokenizer_). It should rather be seen as an in-progress _heuristic_ approach, which will gradually improve as test cases will be reported. This also means that, except for the LIMITATIONS detailed below, there is no known (to the author) SQL code the most current release of this module can't correctly split.\n\nThe test suite bundled with the distribution (which now includes the popular _Sakila_ and _Pagila_ sample db schemata, as detailed in the SHOWCASE section below) should give you an idea of the capabilities of this module\n\nIf your atomic statements are to be fed to a DBMS, you are encouraged to use DBIx::MultiStatementDo instead, which uses this module and also (optionally) offers automatic transactions support, so that you'll have the _all-or-nothing_ behavior you would probably want."
    ],
    "previous_source": "This is a simple module which tries to split any SQL code, even including non-standard extensions (for the details see the the /SUPPORTED DBMSs manpage section below), into the atomic statements it is composed of.\n\nThe logic used to split the SQL code is more sophisticated than a raw 'split' on the ';' (semicolon) character: first, various different statement terminator _tokens_ are recognized (see below for the list), then this module is able to correctly handle the presence of said tokens inside identifiers, values, comments, 'BEGIN ... END' blocks (even nested), _dollar-quoted_ strings, MySQL custom 'DELIMITER's, procedural code etc., as (partially) exemplified in the the /SYNOPSIS manpage above.\n\nConsider however that this is by no means a validating parser (technically speaking, it's just a _context-sensitive tokenizer_). It should rather be seen as an in-progress _heuristic_ approach, which will gradually improve as test cases will be reported. This also means that, except for the the /LIMITATIONS manpage detailed below, there is no known (to the author) SQL code the most current release of this module can't correctly split.\n\nThe test suite bundled with the distribution (which now includes the popular _Sakila_ and _Pagila_ sample db schemata, as detailed in the the /SHOWCASE manpage section below) should give you an idea of the capabilities of this module\n\nIf your atomic statements are to be fed to a DBMS, you are encouraged to use the DBIx::MultiStatementDo manpage instead, which uses this module and also (optionally) offers automatic transactions support, so that you'll have the _all-or-nothing_ behavior you would probably want.",
    "target": [
        "これは単純なモジュールで、標準以外の拡張(詳細は下記の「サポートされているDBMS」のセクションを参照)を含むSQLコードを、構成するアトミックなステートメントに分割しようとします。\n\nSQLコードを分割するために使用されるロジックは、「;」(セミコロン)文字の生の「分割」よりも洗練されています。最初に、さまざまな異なるステートメントterminator_tokens_が認識されます(リストについては以下を参照)。次に、このモジュールは識別子、値、コメント、BEGIN.内のトークンの存在を正しく処理できます。END' ブロック(ネストされている場合も含む)、_dollar-quoted_strings、MySQLカスタムの'DELIMITER'、手続きコードなど、上記の書式で(部分的に)例示したもの。\n\nただし、これは決して検証パーサーではないことを考慮してください(厳密に言えば、単に_context-sensitive tokenizer_です)。むしろ、進行中の_ヒューリスティック_アプローチと見るべきであり、テストケースが報告されるにつれて徐々に改善されるでしょう。これはまた、以下で説明する制限を除いて、このモジュールの最新リリースが正しく分割できない既知のSQLコードが(作成者には)存在しないことを意味します。\n\nこのディストリビューションにバンドルされているテスト・スイート(これには現在、ポピュラーな_Sakila_and_Pagila_sampleデータベース・スキーマが含まれています。これについては、以下のSHOWCASEセクションで詳しく説明します)から、このモジュールの機能を理解することができます。\n\nアトミックな文をDBMSに渡す場合は、代わりにDBIx::MultiStatementDoを使用することをお勧めします。これは、このモジュールを使用し、(オプションで)自動トランザクションサポートも提供するので、おそらく必要な_all-or-nothing_動作を持つことになります。"
    ],
    "id_hash": -6632021309975746951,
    "content_hash": -6632021309975746951,
    "location": "",
    "context": "",
    "note": "tumbleweed/perl-SQL-SplitStatement/description",
    "flags": "",
    "labels": [],
    "state": 20,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 2728,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 247,
    "source_unit": "https://l10n.opensuse.org/api/units/13182537/?format=api",
    "priority": 100,
    "id": 13184011,
    "web_url": "https://l10n.opensuse.org/translate/packages-i18n/perl-master/ja/?checksum=23f653c1ac132679",
    "url": "https://l10n.opensuse.org/api/units/13184011/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2022-02-23T16:53:45.400885Z"
}