-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Prod Promotion -- v0.2.2 #170
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Move to ubicloud * Trigger * Trigger
* refactor: Make tests seperated crate * refactor: Update CI * chore: Clean unnecessary dependency
* Fix CI * Add cache * Rm folder
Signed-off-by: Philippe Noël <21990816+philippemnoel@users.noreply.github.com>
Signed-off-by: Philippe Noël <21990816+philippemnoel@users.noreply.github.com>
Drop reference to AGPL v3.0 and replace with PostgreSQL license Signed-off-by: Thomas Cioppettini <544875+tomciopp@users.noreply.github.com>
* feat: Support for views * chore: Add comments for tests * chore * chore: Update tests * fix: Check if the table exists in the DuckDB * fix: Not fully pushed to DuckDB * chore * chore:test * chore:test * chore: Used sqlparser to parse create view statement * chore: Updated tests * chore: Add comments * chore: Add comments * chore: Fix rebase * chore * refactor: check pgcatalog * chore: Fix typo * chore: Clean up * chore: Warning the table which is not a foreign table from DuckDB * chore: Rebase * refactor: Using parse_analyze_fixedparams * refactor: Update parse_analyze_fixedparams usage in view_query function * refactor: Update parse_analyze_fixedparams usage in view_query function * refactor: Update parse_analyze_fixedparams usage in view_query function and use pg_analyze_and_rewrite_fixedparams instead * fix: CI * chore * chore * chore: Add nested test * chore: Update pg_analytics * chore
A schema difference was detected. A suggested "upgrade.sql" script entry might be: DROP FUNCTION IF EXISTS time_bucket(_bucket_width pg_catalog."interval", _input date);
DROP FUNCTION IF EXISTS time_bucket(_bucket_width pg_catalog."interval", _input date, _offset pg_catalog."interval");
DROP FUNCTION IF EXISTS time_bucket(_bucket_width pg_catalog."interval", _input date, _origin date);
DROP FUNCTION IF EXISTS time_bucket(_bucket_width pg_catalog."interval", _input pg_catalog."timestamp");
DROP FUNCTION IF EXISTS time_bucket(_bucket_width pg_catalog."interval", _input pg_catalog."timestamp", _origin date);
DROP FUNCTION IF EXISTS time_bucket(_bucket_width pg_catalog."interval", _input pg_catalog."timestamp", _offset pg_catalog."interval"); The full diff between both schemas is:331,406d330
< /* <begin connected objects> */
< -- src/api/time_bucket.rs:22
< -- pg_analytics::api::time_bucket::time_bucket
< CREATE FUNCTION "time_bucket"(
< "_bucket_width" interval, /* pgrx::datum::interval::Interval */
< "_input" date /* pgrx::datum::date::Date */
< ) RETURNS date /* pgrx::datum::date::Date */
< STRICT
< LANGUAGE c /* Rust */
< AS 'MODULE_PATHNAME', 'time_bucket_date_wrapper';
< /* </end connected objects> */
<
< /* <begin connected objects> */
< -- src/api/time_bucket.rs:32
< -- pg_analytics::api::time_bucket::time_bucket
< CREATE FUNCTION "time_bucket"(
< "_bucket_width" interval, /* pgrx::datum::interval::Interval */
< "_input" date, /* pgrx::datum::date::Date */
< "_offset" interval /* pgrx::datum::interval::Interval */
< ) RETURNS date /* pgrx::datum::date::Date */
< STRICT
< LANGUAGE c /* Rust */
< AS 'MODULE_PATHNAME', 'time_bucket_date_offset_wrapper';
< /* </end connected objects> */
<
< /* <begin connected objects> */
< -- src/api/time_bucket.rs:27
< -- pg_analytics::api::time_bucket::time_bucket
< CREATE FUNCTION "time_bucket"(
< "_bucket_width" interval, /* pgrx::datum::interval::Interval */
< "_input" date, /* pgrx::datum::date::Date */
< "_origin" date /* pgrx::datum::date::Date */
< ) RETURNS date /* pgrx::datum::date::Date */
< STRICT
< LANGUAGE c /* Rust */
< AS 'MODULE_PATHNAME', 'time_bucket_date_origin_wrapper';
< /* </end connected objects> */
<
< /* <begin connected objects> */
< -- src/api/time_bucket.rs:37
< -- pg_analytics::api::time_bucket::time_bucket
< CREATE FUNCTION "time_bucket"(
< "_bucket_width" interval, /* pgrx::datum::interval::Interval */
< "_input" timestamp /* pgrx::datum::time_stamp::Timestamp */
< ) RETURNS timestamp /* pgrx::datum::time_stamp::Timestamp */
< STRICT
< LANGUAGE c /* Rust */
< AS 'MODULE_PATHNAME', 'time_bucket_timestamp_wrapper';
< /* </end connected objects> */
<
< /* <begin connected objects> */
< -- src/api/time_bucket.rs:42
< -- pg_analytics::api::time_bucket::time_bucket
< CREATE FUNCTION "time_bucket"(
< "_bucket_width" interval, /* pgrx::datum::interval::Interval */
< "_input" timestamp, /* pgrx::datum::time_stamp::Timestamp */
< "_origin" date /* pgrx::datum::date::Date */
< ) RETURNS timestamp /* pgrx::datum::time_stamp::Timestamp */
< STRICT
< LANGUAGE c /* Rust */
< AS 'MODULE_PATHNAME', 'time_bucket_timestamp_offset_date_wrapper';
< /* </end connected objects> */
<
< /* <begin connected objects> */
< -- src/api/time_bucket.rs:51
< -- pg_analytics::api::time_bucket::time_bucket
< CREATE FUNCTION "time_bucket"(
< "_bucket_width" interval, /* pgrx::datum::interval::Interval */
< "_input" timestamp, /* pgrx::datum::time_stamp::Timestamp */
< "_offset" interval /* pgrx::datum::interval::Interval */
< ) RETURNS timestamp /* pgrx::datum::time_stamp::Timestamp */
< STRICT
< LANGUAGE c /* Rust */
< AS 'MODULE_PATHNAME', 'time_bucket_timestamp_offset_interval_wrapper';
< /* </end connected objects> */
< |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket(s) Closed
What
Prepare releasing under PostgreSQL.
Why
How
Tests