home / github

Menu
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

5 rows where issue = 1203842656

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: user, author_association, reactions, created_at (date), updated_at (date)

id ▼ html_url issue_url node_id user created_at updated_at author_association body reactions issue performed_via_github_app
1098537000 https://github.com/simonw/sqlite-utils/issues/425#issuecomment-1098537000 https://api.github.com/repos/simonw/sqlite-utils/issues/425 IC_kwDOCGYnMM5Belgo simonw 9599 2022-04-13T22:18:22Z 2022-04-13T22:18:22Z OWNER I figured out a workaround in https://github.com/simonw/sqlite-utils/issues/421#issuecomment-1098535531 The current `register(fn)` method looks like this: https://github.com/simonw/sqlite-utils/blob/95522ad919f96eb6cc8cd3cd30389b534680c717/sqlite_utils/db.py#L389-L403 This alternative implementation worked in the environment where that failed: ```python def register(fn): name = fn.__name__ arity = len(inspect.signature(fn).parameters) if not replace and (name, arity) in self._registered_functions: return fn kwargs = {} done = False if deterministic: # Try this, but fall back if sqlite3.NotSupportedError try: self.conn.create_function(name, arity, fn, **dict(kwargs, deterministic=True)) done = True except sqlite3.NotSupportedError: pass if not done: self.conn.create_function(name, arity, fn, **kwargs) self._registered_functions.add((name, arity)) return fn ``` {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} `sqlite3.NotSupportedError`: deterministic=True requires SQLite 3.8.3 or higher 1203842656  
1098545390 https://github.com/simonw/sqlite-utils/issues/425#issuecomment-1098545390 https://api.github.com/repos/simonw/sqlite-utils/issues/425 IC_kwDOCGYnMM5Benju simonw 9599 2022-04-13T22:34:52Z 2022-04-13T22:34:52Z OWNER That broke Python 3.7 because it doesn't support `deterministic=True` even being passed: > function takes at most 3 arguments (4 given) {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} `sqlite3.NotSupportedError`: deterministic=True requires SQLite 3.8.3 or higher 1203842656  
1101594549 https://github.com/simonw/sqlite-utils/issues/425#issuecomment-1101594549 https://api.github.com/repos/simonw/sqlite-utils/issues/425 IC_kwDOCGYnMM5BqP-1 simonw 9599 2022-04-18T17:36:14Z 2022-04-18T17:36:14Z OWNER Releated: - #408 {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} `sqlite3.NotSupportedError`: deterministic=True requires SQLite 3.8.3 or higher 1203842656  
1129332959 https://github.com/simonw/sqlite-utils/issues/425#issuecomment-1129332959 https://api.github.com/repos/simonw/sqlite-utils/issues/425 IC_kwDOCGYnMM5DUEDf McEazy2700 102771161 2022-05-17T21:27:02Z 2022-05-17T21:27:02Z NONE Hi, I'm trying to deploy my site using elasticbeanstalk and I keep getting this same error : deterministic=True requires SQLite 3.8.3 or higher I saw your previous solution that involves editing sqlite-utils/sqlite_utils/db.py file, but I'm curious as to how that will work in production. {"total_count": 5, "+1": 5, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} `sqlite3.NotSupportedError`: deterministic=True requires SQLite 3.8.3 or higher 1203842656  
1509951952 https://github.com/simonw/sqlite-utils/issues/425#issuecomment-1509951952 https://api.github.com/repos/simonw/sqlite-utils/issues/425 IC_kwDOCGYnMM5aAAnQ Dhyanesh97 89400147 2023-04-15T20:14:58Z 2023-04-15T20:14:58Z NONE is this change released ? Because when we run docker containers issue still persists for production deployments. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} `sqlite3.NotSupportedError`: deterministic=True requires SQLite 3.8.3 or higher 1203842656  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);
Powered by Datasette · Queries took 42.046ms · About: simonw/datasette-graphql