G🦡Monkey
GreaseMonkey@misskey.resonite.love
安全第二
Posts
-
Post #2393197
ワイルド・スピード MEGA MAX RE: https://misskey.resonite.love/notes/a5s49pizme
-
Post #2393196
オーストラリア、ニュージーランドで5以上がちょっと違う Fast & Furious 5 Fast & Furious 6 Fast & Furious 7 F8: The Fate of the Furious Fast & Furious 9 Fast & Furious X RE: https://misskey.resonite.love/notes/am2pdufid6
-
Post #2393195
1305年じゃないか
-
Post #2201801
第一 ネポチズム 第二 お金がいっぱいになり 第三 嘘安い口を持ち
-
Post #2201800
Unity/UE 💩/🆙
-
Post #2201798
https://www.wheresyoured.at/news-anthropic-removes-pro-cc/
-
Post #2201797
AIくんはPC-98をいつもわからんので全然できない
-
Post #2201796
그것 RE: https://misskey.resonite.love/notes/alec0sxgki
-
Post #2201794
韓国語のIME、エンターキーを使わない、ちょっと変だね
-
Post #2201793
그것: ㄱ ㄱ| ㅡ 그| ㄱ 극| ㅓ 그거| ㅅ 그갓| 그갓| (例えばCtrl)
-
Post #2201790
birdsite = birdして
-
Post #2201788
The problem with the XY problem: You've done a lot of research and thought "this would be a really clean solution to achieve what I want here" (possibly for multiple things), and you request that solution in a feature request. Someone comes along and says "have you considered this instead?" having done no research whatsoever and you've already ruled it out as being a bad solution.
-
Post #2201787
@ratfactor@mastodon.art Saw your sqlite-monotonic-updates card and was thinking that it could be handled quite nicely with triggers. Sorry if someone else has suggested this one. Starting with this table:CREATE TABLE foo (touched int, txt text); We can set up an UPDATE trigger:CREATE TRIGGER foo_touched_update AFTER UPDATE ON FOO BEGIN UPDATE foo SET touched = coalesce((SELECT touched FROM foo ORDER BY touched DESC LIMIT 1), 0)+1 WHERE rowid=new.rowid; END; But we'd also need som...
-
Post #2201786
できた 一回目