Translation status

36 Strings 100%
Browse Translate
698 Words 100%
4,263 Characters 100%

Strings status

Strings Words Characters
36 698 4,263
All strings Browse Translate Zen
36 698 4,263
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
geography_exercises 0 0 0 0 0 0 0
projection_exercises 0 0 0 0 0 0 0
advanced_geometry_construction 0 0 0 0 0 0 0
simple_sql_exercises 0 0 0 0 0 0 0
backup 0 0 0 0 0 0 0
license 0 0 0 0 0 0 0
installation CC-BY-3.0-US 0 0 0 0 0 0 0
knn 0 0 0 0 0 0 0
equality 0 0 0 0 0 0 0
joins_advanced 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar komzpa User avatar dmateos User avatar dkastl User avatar jsanz User avatar andischi User avatar yellow73 User avatar cvvergara User avatar astrid_emde User avatar jef
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 Merge pull request #143 from osgeoweblate/weblate-postgis-workshop-index 4a5082b
Regina Obe authored yesterday
Last commit in Weblate Translated using Weblate (Spanish) 482c6c5
Paulo Cesar authored 2 months ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/schemas.po
Translation file Download postgis-intro/sources/locale/ja/LC_MESSAGES/schemas.po
Last change Oct. 28, 2023, 3:23 a.m.
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 36 698 4,263
Translated 100% 36 100% 698 100% 4,263
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 80 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
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

698
Hosted words
36
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. schemas
  3. Japanese
Changes committed a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
That's all there is to it, the user's default work area is now nicely separated from any tables in other schemas.
これが全てです。これで、ユーザのデフォルト作業領域は、他のスキーマから上手に分割されました。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
The user's search path has the user schema first, so new tables are automatically created there, and queries automatically search there first.
ユーザの検索パスにユーザスキーマが最初に入っていて、新しいテーブルが自動的にそこに生成され、クエリが自動的にそこで最初に実行される。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
The user's named schema exists, and the user owns it.
ユーザ名スキーマが存在し、それをユーザ自身が持っている。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
The user exists, with the ability to create spatial tables.
空間テーブル生成可能なユーザが存在する。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
The first schema on the search path us the user's named schema! So now the following conditions exist:
検索パスの最初のスキーマはユーザ名付きスキーマです! 次の条件が存在します:
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
If you log in as that user, you'll find the default ``search_path`` for PostgreSQL is actually this:
そのユーザとしてログインする場合には、PostgreSQL 用のデフォルトの ``search_path`` が実際に次の通りであることが分かります:
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
Create a new user with table creation privileges (see :ref:`security` for information about the ``postgis_writer`` role), then create a schema with that user as the authorization:
新規ユーザをテーブル生成権限を付けて生成し (``postgis_writer`` ロールの詳細については :ref:`security` をご覧下さい)、その後に、そのユーザに権限付与したスキーマを生成します:
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. schemas
  3. Japanese
By default, every role in Oracle is given a personal schema. This is a nice practice to use for PostgreSQL users too, and is easy to replicate using PostgreSQL roles, schemas, and search paths.
デフォルトでは、Oracle の全てのロールに個別のスキーマが与えられています。これは PostgreSQL ユーザにとっても素晴らしい手法であり、使用している PostgreSQL のロール、スキーマ、検索パスの複製が簡単にできます。
a year ago
User avatar yellow73

Suggestion added

  1. postgis-workshop
  2. schemas
  3. Japanese
That's all there is to it, the user's default work area is now nicely separated from any tables in other schemas.
これが全てです。これで、ユーザのデフォルト作業領域は、他のスキーマから上手に分割されました。
a year ago
Browse all translation changes