#2007: PG data model and functions for Schema #2008

benedeki · 2022-01-11T09:01:38Z

database and database users creation scripts
global_id function
basic tables for entities
tables to store the schema entities
basic function to work with schema entities
first table for statistics

Closes #2007

This is a first suggestion how the Postgres DB for Enceladus should look like, but also the image, how I would like sus to model our database code. Of course that the names and/or logic are not up to question - opposite is true. Please comment, disagree, ask!

Deployment:
The scripts are to be run by a super-user, particularly the first ones.

First execute the scripts in the root.
Then follow by folders
Each folder represent one DB schema - it contains the file _schema.ddl which is to create the schema
Rest are the tables and functions - tables have the extension .ddl, functions .sql.
.sql files are idempotent, can be redeployed repeatedly.
.ddl files are not indempotent,, but usually contain a commented out DROP command which allows redeployment but with a potential data loss.

Then end goal is to have .sql files for functions and .json files describing the tables. A deployment tool then would generate the "migration" to ensure the table are up to the description.

P.S.
Tables in their current format are missing descriptions. Eventually should have them too.

* 1422 and 1423 Remove HDFS and Oozie from Menas * #1422 Fix HDFS location validation * #1424 Add Menas Dockerfile * #1416 hadoop-aws 2.8.5 + s3 aws sdk 2.13.65 compiles. * #1416 - enceladus on S3: - all directly-hdfs touching stuff disabled (atum, performance measurements, info files, output path checking) # Add menasfargate into hosts sudo nano /etc/hosts # paste 20.0.63.69 menasfargate # save & exit (ctrl+O, ctrl+X) # Running standardization works via: spark-submit --class za.co.absa.enceladus.standardization.StandardizationJob --conf "spark.driver.extraJavaOptions=-Dmenas.rest.uri=http://menasfargate:8080 -Dstandardized.hdfs.path=s3://euw1-ctodatadev-dev-bigdatarnd-s3-poc/enceladusPoc/ao-hdfs-data/stdOutput/standardized-{0}-{1}-{2}-{3}" ~/enceladusPoc/spark-jobs-2.11.0-SNAPSHOT.jar --menas-credentials-file ~/enceladusPoc/menas-credentials.properties --dataset-name dk_test1_emr285 --raw-format json --dataset-version 1 --report-date 2019-11-27 --report-version 1 2> ~/enceladusPoc/stderr.txt * #1416 - enceladus on S3 - (crude) conformance works on s3 (s3 std input, s3 conf output) 0- all directly-hdfs touching stuff disabled (atum, performance measurements, info files, output path checking) # Add menasfargate into hosts sudo nano /etc/hosts # paste 20.0.63.69 menasfargate # save & exit (ctrl+O, ctrl+X) # Running conformance works via: spark-submit --class za.co.absa.enceladus.conformance.DynamicConformanceJob --conf "spark.driver.extraJavaOptions=-Dmenas.rest.uri=http://menasfargate:8080 -Dstandardized.hdfs.path=s3://euw1-ctodatadev-dev-bigdatarnd-s3-poc/enceladusPoc/ao-hdfs-data/stdOutput/standardized-{0}-{1}-{2}-{3}" ~/enceladusPoc/spark-jobs-2.11.0-SNAPSHOT.jar --menas-credentials-file ~/enceladusPoc/menas-credentials.properties --dataset-name dk_test1_emr285 --dataset-version 1 --report-date 2019-11-27 --report-version 1 2> ~/enceladusPoc/conf-log.txt * ref issue = 1416 * related test cases ignored (issue reference added) * PR updates * Merge spline 0.5.3 into aws-poc * Update spline to 0.5.4 for AWS PoC * #1503 Remove HDFS url Validation This is a temporary solution. We currently experiment with many forms of URLs, and having a regex there now slows us down. * New dockerfile - smaller image * s3 persistence (atum, sdk fs usage, ...) (#1526) #1526 * FsUtils divided into LocalFsUtils & HdfsUtils * PathConfigSuite update * S3FsUtils with tail-recursive pagination accumulation - now generic with optional short-circuit breakOut TestRunnerJob updated to manually cover the cases - should serve as a basis for tests * HdfsUtils replace by trait DistributedFsUtils (except for MenasCredentials loading & nonSplittable splitting) * using final version of s3-powered Atum (3.0.0) * mockito-update version update, scalatest version update * S3FsUtilsSuite: exists, read, sizeDir(hidden, non-hidden, reucursive), non-splittable (simple, recursive with breakOut), delete (recursive), version find (simple - empty, recursive) * explicit stubbing fix for hyperdrive * Feature/1556 file access PoC using Hadoop FS API (#1586) * s3 using hadoop fs api * s3 sdk usage removed (pom, classes, tests) * atum final version 3.1.0 used * readStandardizationInputData(... path: String)(implicit ... fs: FileSystem) -> readStandardizationInputData(input: PathWithFs) * 1554 Tomcat with TLS in Docker container (#1585) * #1554 Tomcat with TLS container * #1554 Added envoy config + enabling running unencrypted container * #1499 Add authentication to /lineage + update spline to 0.5.5 * #1618 - fixes failing spline 0.5.5 integration by providing compatible commons library version. Test-ran on EMR. (#1619) * #1612 Separation start * #1612 Updated DAO for spark-jobs * #1612 Fixed spline integration and schema, removed redundant code * #1612 Fixed tests, removed unused dependency * #1612 Added back dependency * WIP fixing merge issues * * Merge compiles * Tests pass * Depends on ATUM 3.1.1-SNAPSHOT (the bugfix for AbsaOSS/atum#48) * #1612 Removed Spring from menas-web, enabled building war and static resources. Removed version subpath in menas-web + added theme dependencies in repo * #1612 Cookies + updated lineage * * put back HDFS browser * put back Oozie * downgraded Spline * * AWS SDK Exclusion * #1612 Included HDFSFolder + missing Oozie parts * * New ATUM version * * Adding missing files * #1612 menas-web on nginx container and passing API_URL * #1612 Working TLS on nginx, resources not included in code * 1622: Merge of aws-poc to develop brach * Addressed issues identified by reviewers * * comments improvement * 1434 Add new way of serving properties to Docker * #1612 Building using ui5 + reused /api route * #1612 Project version * #713 Add favicon * #1612 Merges * #1612 pom parent version * #1648 Fix war deployment + adding back spline to menas * #1612 other fixes * #1612 added pom package.json version sync * #1612 newline * #1612 fix version sync + cleaning dist * 1648 merge to develop * 1648 merge fix * 1648 Fixes schema upload * 1648 Fixes schema registry request * 1648 pom version * 1612 add docker build * #601 Swagger 2 PoC * #601 Swagger 2 PoC * #601 Swagger 2 PoC * #1648 Updating menas-web to 3.0 * #1612 Updated npm project versions + mvn plugin * #1612 license_check.yml * #1612 licence check fix Co-authored-by: Saša Zejnilović <zejnils@gmail.com> Co-authored-by: Daniel Kavan <dk1844@gmail.com> Co-authored-by: Jan Scherbaum <kmoj02@gmail.com> Co-authored-by: David Benedeki <benedeki@volny.cz>

% Conflicts: % data-model/src/main/scala/META-INF/MANIFEST.MF % menas-web/ui/components/dataset/conformanceRule/MappingConformanceRule/targetSchemaFieldSelector.fragment.xml % menas/ui/index.html

…ult values

…velop-ver.30 # Conflicts: # menas/src/main/scala/za/co/absa/enceladus/menas/MvcConfig.scala

merging develop into develop-ver3.0 (via feature/merging-develop-ver.30 branch)

KafkaErrorSenderPluginSuite test fix for SourcePhase.{Standardization, Conformance} capitalization.

* #601 Swagger api docs

…XMLHack removed, the test holds. (#1783)

* #1769 rename menas to rest-api * #1769 README update and other feedback

* #1733 final version 0.6.0 of spline spark agent used * #1733 cherrypicked version: commons 0.0.27, atum 3.5.0, spline agent 0.6.0-snapshot * #1733 PR touchup: maven.shade.version version revert to 3.2.1

* #1770 Rename menas-web to menas

% Conflicts: % dao/pom.xml % data-model/pom.xml % examples/pom.xml % menas/pom.xml % migrations-cli/pom.xml % migrations/pom.xml % plugins-api/pom.xml % plugins-builtin/pom.xml % pom.xml % spark-jobs/pom.xml % utils/pom.xml

Spline 0.6 integration

% Conflicts: % menas/pom.xml % menas/ui/index.html % pom.xml % rest-api/src/main/scala/za/co/absa/enceladus/rest_api/WebSecurityConfig.scala % rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/DatasetController.scala

% Conflicts: % menas/pom.xml

…elate to rest_api, not menas: `/3rdParty/**` should not be added anymore as it is menas-related)

* Adding back Menas module, that somehow got omitted.

…lop-ver-3 Merging Release 2.23. 0 into develop ver 3

dk1844

I am by far no expert in SQL (and even less in PG SQL), so I am just mentioning some things I have found a bit unusual (just read the code)

dk1844 · 2022-01-12T13:03:01Z

database/src/main/dataset_schema/add_schema.sql

+DROP FUNCTION IF EXISTS dataset_schema.add_schema(TEXT, INTEGER, TEXT, JSONB, TEXT);
+
+CREATE OR REPLACE FUNCTION dataset_schema.add_schema(


Why dropping the function when you later offer to replace it anyway? (wouldn't either DROP+CREATE or just CREATE or REPLACE suffice?)

You are right. After the DROP CREATE would be enough. I can change that for sure.
(My template is set up with CREATE or REPLACE, but unfortunately it cannot handle if the OUT parameters change - I think it used to have.)

dk1844 · 2022-01-12T13:21:47Z

database/src/main/dataset_schema/add_schema.sql

+--      403     - Schema already exists
+--      404     - Schema version wrong
+--      405     - Schema has been disabled
+--      406     - Schema is locked


This looks like HTTP/REST status codes compatible use, but their usage is quite non-standard. We should not be inventing status codes, I think. How about:

-- 201 - OK -- 409 - (conflict) Schema already exists -- 404 - (not found) Schema version wrong -- 403 - (forbidden) Schema has been disabled -- 403 - (forbidden) Schema is locked

By that I mean:

404 is clear - incorrect path = not found

409 Conflict is typical for out-of-sync edits

for the rest, 403 - forbidden (i.e. request is valid, but the state of the entity does not allow to continue. Here, the difference would have to be documented by the status_text.

If the above is unsatisfactory, perhaps 432 Locked from WebDAV use could be misused, it is pretty close:

-- 409 - (conflict) Schema already exists -- 404 - (not found) Schema version wrong -- 403 - (forbidden) Schema has been disabled -- 423 - (locked) Schema is locked (maybe)

A relevant info source: https://www.restapitutorial.com/httpstatuscodes.html

I am most happy to change the status codes. I didn't put too much effort into their choice. But I would avoid to give the same code to different (failure) reasons, where the text distinguishes them - the first suggestion. The second sounds good, will implement it.

dk1844 · 2022-01-12T13:24:55Z

database/src/main/dataset_schema/get_schema.sql

+-- Status codes:
+--      200     - OK
+--      404     - Schema does not exist
+--      405     - Schema of the given version does not exist


my vote here is to use std 404 code and just differentiate by the status_text

Suggested change

-- 405 - Schema of the given version does not exist

-- 404 - Schema of the given version does not exist

I am happy to use better code, but not the same one, 404.

I understand that you want to distinguish the cases here, but I still believe that 404 is appropriate for both.
The code describes entity requested is not found, how ever defined. So,
get_schema(existingSchema, notExistingVersion) does not exist the same way as get_schema(bogusSchema, regardlessVersion).

Btw. just schema existence, regardless of the version (something that that 405 should signify), can be checked by get_schema(existingSchema, NULL) if I read the code correctly.

405 is Method Not Allowed (by which HTTP methods like GET, POST, ... is meant) so it does not seem to be fitting. So it would be nice to find an alternative status code with a proper meaning, but they don't just give out any 404B's :)

database/src/main/public/global_id.sql

dk1844 · 2022-01-12T13:31:48Z

database/src/main/public/global_id.sql

+ */
+
+
+--DROP SEQUENCE IF  EXISTS public.global_id_seq


Maybe uncomment?

Same as in the case of tables - prevent data loss, potential ID conflict.

database/src/main/public/global_id.sql

dk1844 · 2022-01-12T13:41:27Z

database/src/main/dataset_schema/heads.ddl

+ * limitations under the License.
+ */
+
+-- DROP TABLE dataset_schema.heads;


Suggested change

-- DROP TABLE dataset_schema.heads;

DROP TABLE IF EXISTS dataset_schema.heads;

And the same elsewhere, perhaps?

IF EXISTS sure.
But it's commented out on purpose, so an accidental run won't result in data loss, just an error of trying to create an already existing table.

* added disabled flag in return of list_schemas.sql

AdrianOlosutean · 2022-01-13T10:58:00Z

database/src/main/stats/jobs_configurations.ddl

+
+CREATE TABLE stats.jobs_configurations
+(
+    schema_count        INTEGER NOT NULL,


This was supposed to be landing page statistics? If yes, could you include runs, properties? Also, not sure about the naming

I think some procedures to compute the other fiields like today's run statistics, total number of missing recommended and mandatory properties could be implemented

Adding runs - sure the table can be enhanced easily. But actually I rather expect runs to be in a separate table table. It's update far more frequently, and to avoid blocking and undesired queuing of the requests and little different apraoch might be needed.

Renaming though is a very good comment - what about ENTITIES (I am going to use that, feel free to suggest other. 😉

AdrianOlosutean · 2022-01-13T11:04:16Z

database/src/main/dataset_schema/list_schemas.sql

+    IN  i_include_disabled      BOOLEAN DEFAULT FALSE,
+    OUT schema_name             TEXT,
+    OUT schema_latest_version   INTEGER,
+    OUT disabled                BOOLEAN


Add locked here as well?

We can enhance it if such data are needed. (Adding new columns is backward compatible (older app can qurry such a function without loss of functionality). Right now it seems unnecessary.
disabled was added when I realized it could be little confusing adding the input parameter true but not knowing which are which.

Zejnilovic

Not done, just need a restart.

database/src/main/02_databases.ddl

database/src/main/dataset_schema/add_schema.sql

Zejnilovic · 2022-01-13T11:35:52Z

database/src/main/dataset_schema/get_schema.sql

+    INTO status, status_text, id_schema, schema_name, schema_version,
+         schema_description, fields, created_by, created_when,
+         updated_by, updated_when, locked_by, locked_when,
+        disabled_by, disabled_when;


Suggested change

disabled_by, disabled_when;

disabled_by, disabled_when;

Zejnilovic · 2022-01-13T11:38:58Z

database/src/main/dataset_schema/add_schema.sql

+    ELSIF _disabled THEN
+        status := 405;
+        status_text := 'Schema has been disabled';
+        RETURN ;


Our current Menas re-enables the disabled version. We should come up with a stance on that

Un/locking and En/disabling would be two new functions. Only change the values in the heads table. If we want to keep the I would think to have a journal table.

database/src/main/dataset_schema/add_schema.sql

database/src/main/dataset_schema/get_schema.sql

Zejnilovic · 2022-01-13T12:04:54Z

database/src/main/dataset_schema/list_schemas.sql

+    SELECT dsh.schema_name, dsh.schema_latest_version, dsh.disabled_when IS NOT NULL
+    FROM dataset_schema.heads dsh
+    WHERE i_include_disabled OR dsh.disabled_when IS NULL
+    ORDER BY schema_name; --TODO Include order by?


Current implementation is ordered by version

This is a list of schemas. It doesn't make sense to have it ordered by the schema version when only the latest version number is returned. But reminds me, that a function returning the history (all versions) of a schema will probably be needed.

🤦‍♂️ Sorry, name, it is ordered by name.

This is a list of schemas. It doesn't make sense to have it ordered by the schema version when only the latest version number is returned. But reminds me, that a function returning the history (all versions) of a schema will probably be needed.

I presume these are not all the functions. If they are supposed to be, I will supply the list I come up with

database/src/main/public/global_id.sql

* stats table renamed

* dataset_schema.schemas -> dataset_schema.versions

sonarcloud · 2022-01-14T01:10:27Z

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

* #2022 spark-commons

* New class `TZNormalizedSparkTestBase` used over all tests instead of `SparkTestBase`

* rename of schema files

#2050: Unifying project space with GitHub defaults * docs -> documentation * Milestones are obsolete

* separated DB setup * `..._when` renamed to `..._at`

* shorter function names

…nctions-for-schema

* reordering of OUT parameters in `get`

…ttps://github.com/AbsaOSS/enceladus into feature/2007-pg-data-model-and-functions-for-schema

* stats are row based not column based

* #2034: PG data model and functions for Mapping tables * the tables * Rework for more common naming * * adjust to inherited table * * fixes * * mapping table: path->table_path * * refactored to use connection of entities and versions via id * * white spaces * * add calls _add fix * * check on entities * #2035: PG data model and functions for Dataset (#2054) * #2035: PG data model and functions for Dataset * First commit * * Added check on entity type * * get fucntion * dataset fields * * get comment fixes * * refactored to use id in connection of entities and versions * add function

sonarcloud · 2022-04-26T13:05:53Z

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

benedeki and others added 30 commits March 13, 2021 23:54

Init of Enceladus 3.0.0 develop branch

d109b73

MANIFEST.MFs LF commit

1c7d8a9

Merge branch 'develop' into develop-ver-3.0

836bbec

% Conflicts: % data-model/src/main/scala/META-INF/MANIFEST.MF % menas-web/ui/components/dataset/conformanceRule/MappingConformanceRule/targetSchemaFieldSelector.fragment.xml % menas/ui/index.html

[develop-ver3.0] mergefix

07d4888

changes in Dockerfile - added new ARGs and in menas new ENV with defa…

8a1c171

…ult values

chnaged docker.properties.template and one more ENV for dockerfile

952e52a

spark master and password as before

2b0f371

Merge remote-tracking branch 'origin/develop' into feature/merging-de…

43a2740

…velop-ver.30 # Conflicts: # menas/src/main/scala/za/co/absa/enceladus/menas/MvcConfig.scala

integration

90188dc

Merge branch 'develop' into feature/merging-develop-ver.30

5d3f4e0

SPLINE_URLTEMPLATE moved from docker.prop to Dockerfile

5e90cbd

Merge branch 'develop' into feature/merging-develop-ver.30

42df938

Merge pull request #1752 from AbsaOSS/feature/merging-develop-ver.30

da03de0

merging develop into develop-ver3.0 (via feature/merging-develop-ver.30 branch)

#1774 test fix, the main is unchanged. (#1775)

027f695

KafkaErrorSenderPluginSuite test fix for SourcePhase.{Standardization, Conformance} capitalization.

Feature/601 swagger api docs (#1762)

d3b57a0

* #601 Swagger api docs

#417 SparkXML-related unit test added first (regression guard), Spark…

fa2bbd5

…XMLHack removed, the test holds. (#1783)

#1769 Rename Menas to rest-api (#1781)

88fabeb

* #1769 rename menas to rest-api * #1769 README update and other feedback

Feautre/1733 lineage dumper - 2nd edition (#1766)

70999f5

* #1733 final version 0.6.0 of spline spark agent used * #1733 cherrypicked version: commons 0.0.27, atum 3.5.0, spline agent 0.6.0-snapshot * #1733 PR touchup: maven.shade.version version revert to 3.2.1

1770 Rename menas web to menas (#1786)

c4dcd92

* #1770 Rename menas-web to menas

Merge branch 'develop' into develop-ver-3.0

03f24ba

% Conflicts: % dao/pom.xml % data-model/pom.xml % examples/pom.xml % menas/pom.xml % migrations-cli/pom.xml % migrations/pom.xml % plugins-api/pom.xml % plugins-builtin/pom.xml % pom.xml % spark-jobs/pom.xml % utils/pom.xml

1732 Spline 0.6 integration (#1739)

7f2d6e5

Spline 0.6 integration

Merge branch 'develop' into develop-ver-3.0

f6f0e52

% Conflicts: % menas/pom.xml % menas/ui/index.html % pom.xml % rest-api/src/main/scala/za/co/absa/enceladus/rest_api/WebSecurityConfig.scala % rest-api/src/main/scala/za/co/absa/enceladus/rest_api/controllers/DatasetController.scala

[merging develop->develop-ver-3.0] buildfix

1404bb3

Merge branch 'develop' into develop-ver-3.0

e52c9ff

% Conflicts: % menas/pom.xml

[merging develop->develop-ver-3.0] mergefix

6eea153

[merging develop->develop-ver-3.0] mergefix2 (authorizeRequests now r…

5fa0909

…elate to rest_api, not menas: `/3rdParty/**` should not be added anymore as it is menas-related)

Merge branch 'master' into merge/release-2.23.-0-into-develop-ver-3

c461d22

Merge branch 'master' into merge/release-2.23.-0-into-develop-ver-3

d87e7c3

* Adding back Menas module, that somehow got omitted.

Merge pull request #1890 from AbsaOSS/merge/release-2.23.-0-into-deve…

bd39018

…lop-ver-3 Merging Release 2.23. 0 into develop ver 3

benedeki force-pushed the feature/2007-pg-data-model-and-functions-for-schema branch from 224552d to e8fa5cf Compare January 12, 2022 02:38

benedeki added 2 commits January 12, 2022 12:20

* Reducing sequence cache size

930e963

* More renames from _deleted_ to _disabled_

fefd5f3

dk1844 previously approved these changes Jan 12, 2022

View reviewed changes

* fixed missing version in get_schema.sql

29c5e32

* added disabled flag in return of list_schemas.sql

benedeki dismissed dk1844’s stale review via 29c5e32 January 12, 2022 18:04

AdrianOlosutean reviewed Jan 13, 2022

View reviewed changes

Zejnilovic reviewed Jan 13, 2022

View reviewed changes

benedeki added 2 commits January 13, 2022 16:57

* Addressing PR comments

d1cb905

* stats table renamed

* dataset_schema.heads -> dataset_schema.schemas

eae99fa

* dataset_schema.schemas -> dataset_schema.versions

Adrian-Olosutean and others added 2 commits March 9, 2022 22:05

#2022 spark-commons (#2023)

55696a0

* #2022 spark-commons

#2027: Ensures TimezoneNormalizer is used in tests (#2030)

a10e6b5

* New class `TZNormalizedSparkTestBase` used over all tests instead of `SparkTestBase`

benedeki marked this pull request as draft March 28, 2022 10:13

benedeki and others added 3 commits April 10, 2022 23:29

* status code per new conventions

0634144

* rename of schema files

#2050: Unifying project space with GitHub defaults (#2051)

7e3d599

#2050: Unifying project space with GitHub defaults * docs -> documentation * Milestones are obsolete

* hstore

03cf238

* separated DB setup * `..._when` renamed to `..._at`

benedeki added the work in progress Work on this item is not yet finished (mainly intended for PRs) label Apr 19, 2022

* refactored for inheritance

c698b21

* shorter function names

benedeki removed the work in progress Work on this item is not yet finished (mainly intended for PRs) label Apr 19, 2022

benedeki requested a review from AB006J9 April 19, 2022 21:27

Merge branch 'develop-ver-3.0' into feature/2007-pg-data-model-and-fu…

cb5293c

…nctions-for-schema

benedeki marked this pull request as ready for review April 19, 2022 21:29

benedeki and others added 4 commits April 19, 2022 23:38

* JSONB -> JSON

c368ddf

* reordering of OUT parameters in `get`

Merge branch 'feature/2007-pg-data-model-and-functions-for-schema' of h…

6f7bff6

…ttps://github.com/AbsaOSS/enceladus into feature/2007-pg-data-model-and-functions-for-schema

* entities and versions are connected via id not entity name

ad463f8

* stats are row based not column based

Base automatically changed from develop-ver-3.0 to develop June 3, 2022 13:54

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

#2007: PG data model and functions for Schema #2008

#2007: PG data model and functions for Schema #2008

benedeki commented Jan 11, 2022 •

edited

Loading

dk1844 left a comment •

edited

Loading

dk1844 Jan 12, 2022

benedeki Jan 12, 2022

dk1844 Jan 12, 2022

benedeki Jan 12, 2022

dk1844 Jan 12, 2022

benedeki Jan 12, 2022

dk1844 Jan 20, 2022

dk1844 Jan 12, 2022

benedeki Jan 12, 2022

dk1844 Jan 12, 2022

benedeki Jan 12, 2022

AdrianOlosutean Jan 13, 2022

AdrianOlosutean Jan 13, 2022

benedeki Jan 13, 2022

benedeki Jan 13, 2022

AdrianOlosutean Jan 13, 2022

benedeki Jan 13, 2022

Zejnilovic left a comment

Zejnilovic Jan 13, 2022

Zejnilovic Jan 13, 2022

benedeki Jan 13, 2022

Zejnilovic Jan 13, 2022

benedeki Jan 13, 2022

Zejnilovic Jan 13, 2022

Zejnilovic Jan 13, 2022

sonarcloud bot commented Jan 14, 2022

sonarcloud bot commented Apr 26, 2022

		DROP FUNCTION IF EXISTS dataset_schema.add_schema(TEXT, INTEGER, TEXT, JSONB, TEXT);

		CREATE OR REPLACE FUNCTION dataset_schema.add_schema(

	-- 405 - Schema of the given version does not exist
	-- 404 - Schema of the given version does not exist

	-- DROP TABLE dataset_schema.heads;
	DROP TABLE IF EXISTS dataset_schema.heads;

#2007: PG data model and functions for Schema #2008

Are you sure you want to change the base?

#2007: PG data model and functions for Schema #2008

Conversation

benedeki commented Jan 11, 2022 • edited Loading

dk1844 left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Zejnilovic left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sonarcloud bot commented Jan 14, 2022

sonarcloud bot commented Apr 26, 2022

benedeki commented Jan 11, 2022 •

edited

Loading

dk1844 left a comment •

edited

Loading