Source strings

21 Strings 100%
Browse Translate
583 Words 100%
3,503 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
21 583 3,503
All strings Browse Translate Zen
21 583 3,503
Read-only strings Browse Translate Zen
1 83 466
Strings with any failing checks Browse Translate Zen
1 83 466
Failing check: Ellipsis Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
spatial_relationships_exercises 0 0 0 0 8 0 0
geography_exercises 0 0 0 0 4 0 0
joins_exercises 0 0 0 0 8 0 0
projection_exercises 0 0 0 0 8 0 0
advanced_geometry_construction 0 0 0 0 0 0 0
simple_sql_exercises 0 0 0 0 11 0 0
3d 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
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar komzpa User avatar yellow73 User avatar dmateos User avatar dkastl User avatar astrid_emde User avatar jsanz User avatar andischi User avatar cvvergara 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 #126 from enockseth/fix-typo 9925f56
Paul Ramsey authored yesterday
Last commit in Weblate Translated using Weblate (Japanese) d028968
Teramoto Ikuhiro authored a month ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/clusterindex.po
Translation file Download postgis-intro/sources/locale/pot/clusterindex.pot
Last change Jan. 8, 2023, 2:48 a.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 21 583 3,503
Translated 100% 21 100% 583 100% 3,503
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 21 100% 583 100% 3,503
Failing checks 4% 1 14% 83 13% 466
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 1 change 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

583
Hosted words
21
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

Resource updated

  1. postgis-workshop
  2. clusterindex
  3. English
The "postgis-intro/sources/locale/pot/clusterindex.pot" file was changed. a year ago
User avatar None

Resource updated

  1. postgis-workshop
  2. clusterindex
  3. English
The "postgis-intro/sources/locale/pot/clusterindex.pot" file was changed. a year ago
User avatar None

Resource updated

  1. postgis-workshop
  2. clusterindex
  3. English
The "postgis-intro/sources/locale/pot/clusterindex.pot" file was changed. 2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
`CLUSTER <https://www.postgresql.org/docs/current/sql-cluster.html>`_: Re-orders the data in a table to match the ordering in the index.
`CLUSTER <https://www.postgresql.org/docs/current/sql-cluster.html>`_: Re-orders the data in a table to match the ordering in the index.
2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
The difference between "no index" and "index" is generally huge and highly measurable. The difference between "mediocre index" and "great index" usually takes quite careful measurement to discern, and can be very sensitive to the workload being tested.
The difference between "no index" and "index" is generally huge and highly measurable. The difference between "mediocre index" and "great index" usually takes quite careful measurement to discern, and can be very sensitive to the workload being tested.
2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
In theory, yes. In practice, no really. As long as the index is a "pretty good" spatial decomposition of the data, the main determinant of performance will be the order of the actual table tuples.
In theory, yes. In practice, no really. As long as the index is a "pretty good" spatial decomposition of the data, the main determinant of performance will be the order of the actual table tuples.
2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
Does Index Structure Matter?
Does Index Structure Matter?
2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
System RAM is not the fastest memory on a modern computer. There are several levels of cache between system RAM and the actual CPU, and the underlying operating system and processor will move data up and down the cache heirarchy in blocks. If the block getting moved up happens to include the piece of data the system will need next... that's a big win. Correlating the memory structure with the spatial structure is a way in increase the odds of that win happening.
System RAM is not the fastest memory on a modern computer. There are several levels of cache between system RAM and the actual CPU, and the underlying operating system and processor will move data up and down the cache heirarchy in blocks. If the block getting moved up happens to include the piece of data the system will need next... that's a big win. Correlating the memory structure with the spatial structure is a way in increase the odds of that win happening.
2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
Surprisingly, yes. Keeping records that are "near each other" in space "near each other" in memory increases the odds that related records will move up the servers "memory cache heirarchy" together, and thus make memory accesses faster.
Surprisingly, yes. Keeping records that are "near each other" in space "near each other" in memory increases the odds that related records will move up the servers "memory cache heirarchy" together, and thus make memory accesses faster.
2 years ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. clusterindex
  3. English
Is clustering still necessary?
Is clustering still necessary?
2 years ago
Browse all translation changes