Translation status

42 Strings
100%
Browse Translate
856 Words
100%
5,039 Characters
100%

Strings status

Strings Words Characters
42 856 5,039
All strings Browse Translate Zen
42 856 5,039
Translated strings Browse Translate Zen

Summary

Project website postgis.net/workshops/postgis-intro
Project maintainers9 User avatar cvvergaraUser avatar dkastlUser avatar komzpaUser avatar astrid_emdeUser avatar dmateosUser avatar jsanzUser avatar andischiUser avatar jefUser avatar yellow73
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/postgis/postgis-workshops.git
Repository branch master
Last remote commit Update sql cheat sheet with makevalid example 5f99414
Paul Ramsey authored 10/30/2025
Last commit in Weblate Translated using Weblate (Spanish) 1964869
Paulo Cesar Coronado authored 08/31/2025
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/history_tracking.po
Translation file Download postgis-intro/sources/locale/ja/LC_MESSAGES/history_tracking.po
Last change July 21, 2023, 7:22 a.m.
Last change made by Teramoto Ikuhiro
Language Japanese
Language code ja
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 117,608,755
Number of plurals 1
Plural type None
Plurals
Plural formula 0
02/15/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 42 856 5,039
Translated 100% 42 100% 856 100% 5,039
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

856
Hosted words
42
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar yellow73

Suggestion accepted
History tracking works by keeping a history table that records, for every edit:
編集操作ごとに記録する履歴テーブルを維持することで履歴追跡が働きます。:
07/21/2023
User avatar yellow73

Suggestion accepted
`PostgreSQL Range Types <https://www.postgresql.org/docs/current/rangetypes.html>`_
`PostgreSQL 範囲型 <https://www.postgresql.jp/document/current/html/rangetypes.html>`_
07/21/2023
User avatar yellow73

Suggestion accepted
`PostgreSQL Triggers <http://www.postgresql.org/docs/current/static/plpgsql-trigger.html>`_
`PostgreSQL トリガ関数 <https://www.postgresql.jp/document/current/html/plpgsql-trigger.html>`_
07/21/2023
User avatar yellow73

Suggestion accepted
`QGIS open source GIS <http://qgis.org>`_
`QGIS フリーでオープンソースの地理情報システム <http://qgis.org>`_
07/21/2023
User avatar yellow73

Suggestion accepted
We can also create views that show just what a particular used has added, for example:
特定の使用者が追加したものだけを表示するビューを作ることもできます。次のようにします:
07/21/2023
User avatar yellow73

Suggestion accepted
We can use this logic to create a query, or a view, of the state of the data in the past. Since presumably all your test edits have happened in the past couple minutes, let's create a view of the history table that shows the state of the table 10 minutes ago, **before you started editing** (so, the original data).
このロジックを使って、過去のデータ状況のクエリやビューを生成できます。おそらく全ての試験編集は過去数分に行われているので、**編集開始前** (つまりオリジナルデータ) である、10分前のテーブルの状況を示す履歴テーブルのビューを生成してみましょう。
07/21/2023
User avatar yellow73

Suggestion accepted
All records created before T, but deleted **after** T.
T の前に作られるが T の後に削除された全てのレコード。
07/21/2023
User avatar yellow73

Suggestion accepted
All records created before T, and not yet deleted; and also
T の前に作られ、まだ削除されていない全てのレコードと、さらに
07/21/2023
User avatar yellow73

Suggestion accepted
Now that we have a history table, what use is it? It's useful for time travel! To travel to a particular time **T**, you need to construct a query that includes:
現在、履歴テーブルを持っています。どういう用途でしょうか? 時間旅行に使うのです! 特定の時刻 **T** に行くには、次を含むクエリを構築する必要があります:
07/21/2023
User avatar yellow73

Suggestion accepted
Updating the two streets will cause the original streets to be marked as deleted in the history table, with a deletion time of now, and two new streets with the new name added, with an addition time of now. You can inspect the historical records:
二つのストリートの更新によって、履歴テーブルでは元のストリートに削除済みマーク、削除時刻が付き、二つの名前が変更された新しいストリートが追加され、現在時刻が付きます。履歴レコードを調べることができます:
07/21/2023
Browse all translation changes