id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,pull_request,body,repo,type,active_lock_reason,performed_via_github_app,reactions,draft,state_reason
564833696,MDU6SXNzdWU1NjQ4MzM2OTY=,670,Prototoype for Datasette on PostgreSQL,9599,open,0,,,15,2020-02-13T17:17:55Z,2023-11-17T15:32:21Z,,OWNER,,"I thought this would never happen, but now that I'm deep in the weeds of running SQLite in production for Datasette Cloud I'm starting to reconsider my policy of only supporting SQLite.

Some of the factors making me think PostgreSQL support could be worth the effort:
- Serverless. I'm getting increasingly excited about writable-database use-cases for Datasette. If it could talk to PostgreSQL then users could easily deploy it on Heroku or other serverless providers that can talk to a managed RDS-style PostgreSQL.
- Existing databases. Plenty of organizations have PostgreSQL databases. They can export to SQLite using [db-to-sqlite](https://github.com/simonw/db-to-sqlite) but that's a pretty big barrier to getting started - being able to run `datasette postgresql://connection-string` and start trying it out would be a massively better experience.
- Data size. I keep running into use-cases where I want to run Datasette against many GBs of data. SQLite can do this but PostgreSQL is much more optimized for large data, especially given the existence of tools like Citus.
- Marketing. Convincing people to trust their data to SQLite is potentially a big barrier to adoption. Even if I've convinced myself it's trustworthy I still have to convince everyone else.
- It might not be that hard? If this required a ground-up rewrite it wouldn't be worth the effort, but I have a hunch that it may not be too hard - most of the SQL in Datasette should work on both databases since it's almost all portable SELECT statements. If Datasette did DML this would be a lot harder, but it doesn't.
- Plugins! This feels like a natural surface for a plugin - at which point people could add MySQL support and suchlike in the future.

The above reasons feel strong enough to justify a prototype.",107914493,issue,,,"{""url"": ""https://api.github.com/repos/simonw/datasette/issues/670/reactions"", ""total_count"": 19, ""+1"": 14, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 5, ""rocket"": 0, ""eyes"": 0}",,
564579430,MDU6SXNzdWU1NjQ1Nzk0MzA=,86,Problem with square bracket in CSV column name,8149512,closed,0,,,7,2020-02-13T10:19:57Z,2020-02-27T04:16:08Z,2020-02-27T04:16:07Z,NONE,,"testing some data from european power information (entsoe.eu), the title of the csv contains square brackets.
as I am playing with glitch, sqlite-utils are used for creating the db.

Traceback (most recent call last):

  File ""/app/.local/bin/sqlite-utils"", line 8, in <module>

    sys.exit(cli())

  File ""/app/.local/lib/python3.7/site-packages/click/core.py"", line 764, in __call__

    return self.main(*args, **kwargs)

  File ""/app/.local/lib/python3.7/site-packages/click/core.py"", line 717, in main

    rv = self.invoke(ctx)

  File ""/app/.local/lib/python3.7/site-packages/click/core.py"", line 1137, in invoke

    return _process_result(sub_ctx.command.invoke(sub_ctx))

  File ""/app/.local/lib/python3.7/site-packages/click/core.py"", line 956, in invoke

    return ctx.invoke(self.callback, **ctx.params)

  File ""/app/.local/lib/python3.7/site-packages/click/core.py"", line 555, in invoke

    return callback(*args, **kwargs)

  File ""/app/.local/lib/python3.7/site-packages/sqlite_utils/cli.py"", line 434, in insert

    default=default,

  File ""/app/.local/lib/python3.7/site-packages/sqlite_utils/cli.py"", line 384, in insert_upsert_implementation

    docs, pk=pk, batch_size=batch_size, alter=alter, **extra_kwargs

  File ""/app/.local/lib/python3.7/site-packages/sqlite_utils/db.py"", line 997, in insert_all

    extracts=extracts,

  File ""/app/.local/lib/python3.7/site-packages/sqlite_utils/db.py"", line 618, in create

    extracts=extracts,

  File ""/app/.local/lib/python3.7/site-packages/sqlite_utils/db.py"", line 310, in create_table

    self.conn.execute(sql)

sqlite3.OperationalError: unrecognized token: ""]""

entsoe_2016.csv

renamed to txt for uploading compatibility

[entsoe_2016.txt](https://github.com/simonw/sqlite-utils/files/4197688/entsoe_2016.txt)

code is remixed directly from your https://glitch.com/edit/#!/datasette-csvs repo
",140912432,issue,,,"{""url"": ""https://api.github.com/repos/simonw/sqlite-utils/issues/86/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed