(Obsolete) Set category tracking level defaults historically

[jomaxro (Joshua Rosenfeld)]

It looks like you’re typing %? Don’t . That’s just supposed to be an indication that you’re in the rails console instead of the docker container. I’ll edit the OP to be clearer.

Edit: OP edited.

[SouperC (NotSoSuper)]

Thanks. Rookie error on my part

[jomaxro (Joshua Rosenfeld)]

No worries at all. We all start from the beginning at some point.

Is the guide clearer now?

[SouperC (NotSoSuper)]

@jomaxro

Is the guide clearer now?

Oh it makes total sense. Thanks

[SouperC (NotSoSuper)]

Actually… I’m stuck on the query. I need to update category ID 1 to notification level of regular (1).
From rails… I’m typing

User.exec_sql("INSERT INTO category_users(category_id, user_id, notification_level) SELECT 1, u.id, 1 FROM users u LEFT JOIN category_users cu ON cu.category_id = 1 AND cu.user_id = u.id WHERE cu.user_id IS NULL;")

I get response

<PG::Result:0x000055fadb534428 status=PGRES_COMMAND_OK ntuples=0 nfields=0 cmd_tuples=0>

Via the GUI/forums, it looks like it hasn’t changed.

[jomaxro (Joshua Rosenfeld)]

Going to call in an assist here from @sam, PostgreSQL isn’t my area of expertise.

[SouperC (NotSoSuper)]

Circling back to see if anyone has ideas on where I’m going wrong with my sql query?

[david (David Taylor)]

The query you tried will only update the tracking level IF the user isn’t already tracking/watching/muting a category. It sounds like you want to remove any users that are watching a category.

If that’s correct, try running this on the rails console. It will find all users that are ‘watching’ the category with id=5, and set them to “regular”:

CategoryUser.where(notification_level: CategoryUser.notification_levels[:watching], category_id: 5).update_all(notification_level: CategoryUser.notification_levels[:regular])

As always, make sure to take a backup before running anything on the console - the smallest typo can have massive consequences!

[SouperC (NotSoSuper)]

Thanks David. I must have misunderstood the purpose of the query. I thought it was to update (ie lower the subscription level) for all users UNLESS they explicitly set it themselves vs it being assigned via the setting in admin panel.

[david (David Taylor)]

@SouperC

for all users UNLESS they explicitly set it themselves

The more precise definition here is “for all users UNLESS it has already been set”. We don’t have any way of knowing whether a user set it themselves, or it was automatically set by the admin panel default.

[SouperC (NotSoSuper)]

@david

We don’t have any way of knowing whether a user set it themselves, or it was automatically set by the admin panel default

That makes sense because when I (thought I) saw that, I thought “well that’s impressive that we have that granularity”

[SouperC (NotSoSuper)]

Not to be a pest, but I’m still struggling with this, getting a syntax error when I run this query…

[4] pry(main)> User.exec_sql("INSERT INTO CategoryUser.where(notification_level: CategoryUser.notification_levels[:watching], category_id: 1).update_all(notification_level: CategoryUser.notification_levels[:regular];")

PG::SyntaxError: ERROR:  syntax error at or near ":"
LINE 1: INSERT INTO CategoryUser.where(notification_level: CategoryU...

Any ideas on what I’m overlooking?

[david (David Taylor)]

Sorry, I should have been clearer there. The command I shared does not need to be run inside “exec_sql”. It can just be run directly on the rails console.

[SouperC (NotSoSuper)]

Sorry to spam the topic with this more rudimentary stuff. I’m still having difficulties

From the rails console (at least I think it is)

/var/discourse# ./launcher rails c
/var/discourse# CategoryUser.where(notification_level: CategoryUser.notification_levels[:watching], category_id: 1).update_all(notification_level: CategoryUser.notification_levels[:regular])

bash: syntax error near unexpected token `notification_level:’

[sam (Sam Saffron)]

@SouperC

bash: syntax error near unexpected token `notification_level:’

You are missing a:

rails c before running the command. You want to be in Ruby not in Bash.

[pfaffman (Jay Pfaffman)]

You need to run that inside the container.

./launcher enter app

Before the rails command

[SouperC (NotSoSuper)]

Thanks Jay. Yeah I figured that out while I was working on it today. The trigger being when I was prompted to install rails

I got this to work today, checked a few accounts via impersonate and it looks like we’ll no longer be spamming our members with 100emails a day (nor paying to send them)

Thanks all

James

[barreeeiroo (Diego Barreiro)]

我想这需要一些时间才能完成，对吧？
因为命令输出是即时的，结果如下：
#<PG::Result:0x000055e37f159100 status=PGRES_COMMAND_OK ntuples=0 nfields=0 cmd_tuples=8428>
完成可能需要多久？因为我检查了一个用户资料，发现它仍在关注该类别。

[jomaxro (Joshua Rosenfeld)]

这应该几乎是瞬间完成的。该输出显示已更改 8,428 条记录。我假设这是您论坛的用户数量？建议您再次确认是否正确设置了类别 ID 和通知级别 ID。

[barreeeiroo (Diego Barreiro)]

那不是我要找的查询

这个可以工作：

CategoryUser.where(notification_level: CategoryUser.notification_levels[:watching], category_id: 29).update_all(notification_level: CategoryUser.notification_levels[:regular])

就是 @david 上面发布的那个