Skip to content
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

Some small tweaks to Red. #404

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Some small tweaks to Red. #404

wants to merge 8 commits into from

Conversation

xinminglai
Copy link
Contributor

Hi, These 3 patches add method column-values, and some small fixes for Red::Driver::Pg

Thanks!

@FCO
Copy link
Owner

FCO commented Nov 2, 2019

It seems 2 tests are failing with these changes...

@@ -34,6 +34,22 @@ multi method translate(Red::AST::Select $_, $context?, :$gambi where !*.defined)
self.Red::Driver::CommonSQL::translate($_, $context, :gambi);
}

multi method translate(Red::AST::In $_, $context?) {
if .right.value ~~ Positional {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you, please, put this test on the signature and remove the else?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean something like:

multi method translate(Red::AST::In $_ where .right.value ~~ Positional, $context?) {

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But, instead of testing the right's value type, it would be better to test if it's an Red::AST::Value and if its .type is Positional.

multi method translate(Red::AST::In $_ where .right ~~ Red::AST::Value && .right.type ~~ Positional, $context?) {

my ($lstr, @lbind) := do given self.translate: .left, $context { .key, .value }

if .right.value.elems == 0 {
return "$lstr { .op } (SELECT 0 WHERE false)" => @lbind;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why change to use in (SELECT 0 WHERE false)? why not in ()?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because In Pg, the in () will raise error, So, we should add placehoder statement to select "nothing".

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that way, maybe we could do an:

multi method translate(Red::AST::In $_ where .right ~~ Red::AST::Value && .right.type ~~ Positional && .right.elems, $context?) {

?

@@ -34,6 +34,22 @@ multi method translate(Red::AST::Select $_, $context?, :$gambi where !*.defined)
self.Red::Driver::CommonSQL::translate($_, $context, :gambi);
}

multi method translate(Red::AST::In $_, $context?) {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it common? Couldn't it be on CommonSQL?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's common, But It's strange that it works in SQLite.

return "$lstr { .op } (SELECT 0 WHERE false)" => @lbind;
}

my $in-placeholder = '(' ~ (self.wildcard xx .right.value.elems).join(',') ~ ')';
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you fix one of my errors (https://github.com/FCO/Red/blob/master/lib/Red/Driver/CommonSQL.pm6#L521) changing "?" to self.wildcard, you could just use the self.translate: .right, $context

@@ -111,6 +127,10 @@ multi method default-type-for(Red::Column $ where .attr.type ~~ Bool
multi method default-type-for(Red::Column $ where .attr.type ~~ UUID --> Str:D) {"uuid"}
multi method default-type-for(Red::Column $ --> Str:D) {"varchar(255)"}

multi method type-by-name("text" --> "text") {}
multi method type-by-name("json" --> "json") {}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you, please, add a test for json and jsonb?

for SQLite, it re-fetches the row from the model by using LastInsertedRow
class, Then the `.row{@ids}` does the right thing all the time. But in
postgres, the $data will filled by `INSERT INTO table xxx RETURNING *` after
the RETURNING, we'll $data with column names with underscores.
So, in the pg case, We convert the $data structure according to the model, make
$data look like the same as fetched with LastInsertedRow class.

model Category is table<test_category> {
has Int $.id is serial;
has Int $.parent_id is column{ :references{ Category.id }, :nullable, };
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is failing here. For Red:api<2> you need to set the :model<> for is referencing or :model-name<> in this case... and receive the model type as parameter:

has Int $.parent_if is column{ :references{ .id }, :nullable };

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants