Changes
Translation components API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/components/postgis-workshop/schemas/changes/?format=api&page=3
https://weblate.osgeo.org/api/components/postgis-workshop/schemas/changes/?format=api&page=4", "previous": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/changes/?format=api&page=2", "results": [ { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/sv/?format=api", "user": "https://weblate.osgeo.org/api/users/yeager/?format=api", "author": null, "timestamp": "2025-06-04T15:19:15.909352Z", "action": 17, "target": "", "id": 2135104, "action_name": "Changes committed", "url": "https://weblate.osgeo.org/api/changes/2135104/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": null, "author": null, "timestamp": "2025-03-14T05:47:36.014771Z", "action": 17, "target": "", "id": 2037607, "action_name": "Changes committed", "url": "https://weblate.osgeo.org/api/changes/2037607/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98307/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:17:55.570337Z", "action": 5, "target": "Creando un Esquema de Datos", "id": 2037601, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037601/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98305/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:17:38.062498Z", "action": 5, "target": "Así pues, a efectos de producción, mantener los datos de la aplicación separados en esquemas mejora la gestión; y a efectos de usuario, mantener a los usuarios en esquemas separados evita que la colisión no deseada de actividades entre ellos.", "id": 2037600, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037600/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98303/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:16:32.772981Z", "action": 5, "target": "El trabajo de los usuarios puede limitarse a esquemas únicos para aislar las tablas analíticas y de prueba de las tablas de producción.", "id": 2037599, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037599/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98301/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:16:11.468260Z", "action": 5, "target": "Es más fácil gestionar los cambios en la aplicación cuando los datos de la aplicación están en un esquema: así, una nueva versión del software puede funcionar con una estructura de tablas en un nuevo esquema, y la transición implica un simple cambio en el nombre del esquema.", "id": 2037598, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037598/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98299/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:15:13.338652Z", "action": 5, "target": "Es más fácil restaurar datos que están en un esquema separado: así, los esquemas orientados a aplicaciones pueden restaurarse por separado y se puede hacer una copia de seguridad de ellos para recuperarlos.", "id": 2037597, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037597/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98297/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:14:39.665662Z", "action": 5, "target": "Es más fácil hacer copias de seguridad de datos que están en un esquema separado: así, los datos volátiles pueden tener un programa de copias de seguridad diferente del de los datos no volátiles.", "id": 2037596, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037596/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98295/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:14:03.964107Z", "action": 5, "target": "A los datos que se gestionan en un esquema se puede aplicar acciones masivas con facilidad.", "id": 2037595, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037595/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98293/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:13:15.676129Z", "action": 5, "target": "Hay dos buenas razones para utilizar esquemas:", "id": 2037594, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037594/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98291/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:12:58.259124Z", "action": 5, "target": "¿Por qué usar esquemas?", "id": 2037593, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037593/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98289/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:12:41.318423Z", "action": 5, "target": "En el esquema público también puedes ver todas las tablas que hemos creado hasta ahora en el taller.", "id": 2037592, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037592/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98287/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:12:21.668968Z", "action": 5, "target": "Dentro de ese esquema, la instalación predeterminada de PostGIS crea las relaciones de metadatos ``geometry_columns``, ``geography_columns`` y ``spatial_ref_sys``, así como todos los tipos y funciones utilizados por PostGIS. Así que los usuarios de PostGIS siempre necesitan acceder al esquema público.", "id": 2037591, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037591/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98285/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:11:37.789050Z", "action": 5, "target": "Los esquemas son como carpetas y pueden contener tablas, vistas, funciones, secuencias y otras relaciones. Toda base de datos comienza con un esquema, el esquema ``público``.", "id": 2037590, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037590/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98284/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:11:09.617930Z", "action": 2, "target": "Las bases de datos de producción inevitablemente tienen un gran número de tablas y vistas, y administrarlas puede volverse difícil. Afortunadamente, PostgreSQL_ incluye el concepto de \"_Schema\".", "id": 2037589, "action_name": "Translation changed", "url": "https://weblate.osgeo.org/api/changes/2037589/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98284/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:10:49.407882Z", "action": 5, "target": "Las bases de datos de producción inevitablemente tienen un gran número de tablas y vistas, y administrarlas puede volverse difícil. Afortunadamente, PostgreSQL_ incluye el concepto de \"_Esquema\".", "id": 2037588, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037588/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98283/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:09:58.624907Z", "action": 5, "target": "Esquemas en Postgresql", "id": 2037587, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2037587/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98283/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "author": "https://weblate.osgeo.org/api/users/paulocoronado/?format=api", "timestamp": "2025-03-14T05:09:58.622154Z", "action": 45, "target": "", "id": 2037586, "action_name": "Contributor joined", "url": "https://weblate.osgeo.org/api/changes/2037586/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98171/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/de/?format=api", "user": "https://weblate.osgeo.org/api/users/anonymous/?format=api", "author": "https://weblate.osgeo.org/api/users/anonymous/?format=api", "timestamp": "2024-09-24T15:26:26.659490Z", "action": 4, "target": "PostgresSQL Schemas", "id": 1995219, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1995219/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": null, "author": null, "timestamp": "2023-10-28T03:23:45.312967Z", "action": 17, "target": "", "id": 1894690, "action_name": "Changes committed", "url": "https://weblate.osgeo.org/api/changes/1894690/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98464/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:42:25.119046Z", "action": 7, "target": "これが全てです。これで、ユーザのデフォルト作業領域は、他のスキーマから上手に分割されました。", "id": 1894408, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894408/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98462/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:42:18.935766Z", "action": 7, "target": "ユーザの検索パスにユーザスキーマが最初に入っていて、新しいテーブルが自動的にそこに生成され、クエリが自動的にそこで最初に実行される。", "id": 1894407, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894407/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98460/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:42:13.923689Z", "action": 7, "target": "ユーザ名スキーマが存在し、それをユーザ自身が持っている。", "id": 1894406, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894406/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98458/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:42:08.444338Z", "action": 7, "target": "空間テーブル生成可能なユーザが存在する。", "id": 1894405, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894405/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98457/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:42:03.757073Z", "action": 7, "target": "検索パスの最初のスキーマはユーザ名付きスキーマです! 次の条件が存在します:", "id": 1894404, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894404/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98455/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:56.886797Z", "action": 7, "target": "そのユーザとしてログインする場合には、PostgreSQL 用のデフォルトの ``search_path`` が実際に次の通りであることが分かります:", "id": 1894403, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894403/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98453/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:51.192128Z", "action": 7, "target": "新規ユーザをテーブル生成権限を付けて生成し (``postgis_writer`` ロールの詳細については :ref:`security` をご覧下さい)、その後に、そのユーザに権限付与したスキーマを生成します:", "id": 1894402, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894402/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98452/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:46.244924Z", "action": 7, "target": "デフォルトでは、Oracle の全てのロールに個別のスキーマが与えられています。これは PostgreSQL ユーザにとっても素晴らしい手法であり、使用している PostgreSQL のロール、スキーマ、検索パスの複製が簡単にできます。", "id": 1894401, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1894401/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98464/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.871469Z", "action": 4, "target": "これが全てです。これで、ユーザのデフォルト作業領域は、他のスキーマから上手に分割されました。", "id": 1894400, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894400/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98462/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.866907Z", "action": 4, "target": "ユーザの検索パスにユーザスキーマが最初に入っていて、新しいテーブルが自動的にそこに生成され、クエリが自動的にそこで最初に実行される。", "id": 1894399, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894399/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98460/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.862456Z", "action": 4, "target": "ユーザ名スキーマが存在し、それをユーザ自身が持っている。", "id": 1894398, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894398/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98458/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.853978Z", "action": 4, "target": "空間テーブル生成可能なユーザが存在する。", "id": 1894397, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894397/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98457/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.849358Z", "action": 4, "target": "検索パスの最初のスキーマはユーザ名付きスキーマです! 次の条件が存在します:", "id": 1894396, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894396/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98455/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.844648Z", "action": 4, "target": "そのユーザとしてログインする場合には、PostgreSQL 用のデフォルトの ``search_path`` が実際に次の通りであることが分かります:", "id": 1894395, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894395/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98453/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.840004Z", "action": 4, "target": "新規ユーザをテーブル生成権限を付けて生成し (``postgis_writer`` ロールの詳細については :ref:`security` をご覧下さい)、その後に、そのユーザに権限付与したスキーマを生成します:", "id": 1894394, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894394/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98452/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-27T02:41:20.824937Z", "action": 4, "target": "デフォルトでは、Oracle の全てのロールに個別のスキーマが与えられています。これは PostgreSQL ユーザにとっても素晴らしい手法であり、使用している PostgreSQL のロール、スキーマ、検索パスの複製が簡単にできます。", "id": 1894393, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1894393/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": null, "user": null, "author": null, "timestamp": "2023-10-19T03:55:09.185728Z", "action": 47, "target": "", "id": 1888253, "action_name": "Alert triggered", "url": "https://weblate.osgeo.org/api/changes/1888253/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": null, "author": null, "timestamp": "2023-10-16T14:23:45.052234Z", "action": 17, "target": "", "id": 1884462, "action_name": "Changes committed", "url": "https://weblate.osgeo.org/api/changes/1884462/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98450/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:21.815189Z", "action": 7, "target": "ユーザはテーブルの作成を好みますが、PostGIS ユーザは特に好みます。SQL を使った分析演算には、可視化や中間結果のための一時テーブルが必要で、空間 SQL では、通常のデータベース作業より、ユーザが CREATE 権限を持つことが求められる傾向にあります。", "id": 1884445, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884445/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98432/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:16.877208Z", "action": 7, "target": "運用目的では、アプリケーションデータをスキーマで分離するようにすることで、管理が改善します。ユーザ目的では、分離したスキーマのユーザが互いに踏みつけあうことを防ぎます。", "id": 1884444, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884444/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98431/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:15.039629Z", "action": 7, "target": "ユーザ作業を単一スキーマに制限することができ、これによって分析テーブルとテストテーブルを運用テーブルから分離できます。", "id": 1884443, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884443/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98430/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:13.088814Z", "action": 7, "target": "アプリケーションデータがスキーマ内にある時には、アプリケーションの差異の管理が簡単になるので、新しいバージョンのソフトウェアは、新しいスキーマ内のテーブル構造を処理して、カットオーバーの際はスキーマ名の単純な変更を行います。", "id": 1884442, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884442/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98429/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:11.087933Z", "action": 7, "target": "別のスキーマへのデータの格納は簡単ですので、アプリケーション指向のスキーマは、タイムトラベルとリカバリのための、個別の格納とバックアップが可能です。", "id": 1884441, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884441/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98428/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:08.493434Z", "action": 7, "target": "別のスキーマ内のデータのバックアップの方が簡単ですので、揮発性データと不揮発データとはバックアップスケジュールが異なります。", "id": 1884440, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884440/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98427/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:06:06.162623Z", "action": 7, "target": "スキーマ内で管理されるデータは一括処理に適用しやすいです。", "id": 1884439, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884439/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98424/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:05:50.517444Z", "action": 2, "target": "public スキーマ内では、ワークショップでこれまでに生成してきたテーブルの全てを見ることができます。", "id": 1884438, "action_name": "Translation changed", "url": "https://weblate.osgeo.org/api/changes/1884438/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98424/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:05:44.117855Z", "action": 7, "target": "\"public\" スキーマ内では、ワークショップでこれまでに生成してきたテーブルの全てを見ることができます。", "id": 1884437, "action_name": "Suggestion accepted", "url": "https://weblate.osgeo.org/api/changes/1884437/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98450/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:05:30.679976Z", "action": 4, "target": "ユーザはテーブルの作成を好みますが、PostGIS ユーザは特に好みます。SQL を使った分析演算には、可視化や中間結果のための一時テーブルが必要で、空間 SQL では、通常のデータベース作業より、ユーザが CREATE 権限を持つことが求められる傾向にあります。", "id": 1884436, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1884436/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98432/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:05:30.662620Z", "action": 4, "target": "運用目的では、アプリケーションデータをスキーマで分離するようにすることで、管理が改善します。ユーザ目的では、分離したスキーマのユーザが互いに踏みつけあうことを防ぎます。", "id": 1884435, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1884435/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/98431/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/schemas/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/schemas/ja/?format=api", "user": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "author": "https://weblate.osgeo.org/api/users/yellow73/?format=api", "timestamp": "2023-10-16T10:05:30.657231Z", "action": 4, "target": "ユーザ作業を単一スキーマに制限することができ、これによって分析テーブルとテストテーブルを運用テーブルから分離できます。", "id": 1884434, "action_name": "Suggestion added", "url": "https://weblate.osgeo.org/api/changes/1884434/?format=api" } ] }{ "count": 226, "next": "