Sqlite supports memory database for test purpose

[lunny]

To make tests run faster, allow sqlite's PATH as a :memory: which means run sqlite memory-only. The data will disappear when Gitea or Gitea test exit.

[wxiaoguang]

It is not right to use :memory:

[lunny]

It is not right to use :memory:

ref from https://github.com/mattn/go-sqlite3?tab=readme-ov-file#faq

[wxiaoguang]

cache=shared is a must if you use :memory:, but cache=shared is also highly discouraged: https://www.sqlite.org/sharedcache.html

I do not see real benefits to play with them.

[lunny]

cache=shared is a must if you use :memory:, but cache=shared is also highly discouraged: sqlite.org/sharedcache.html

I do not see real benefits to play with them.

I think this is the only method to use memory because memory cannot be used with WAL. https://sqlite.org/forum/info/a44bddd65750d084

[wxiaoguang]

But the sqlite tests are fast enough, I do not think these tricks would save more minutes.

The slowest test is still mysql

[lunny]

And I think we already used :memory: in our unit test.

gitea/models/unittest/testdb.go

Line 206 in 5d57c28

x, err := xorm.NewEngine("sqlite3", "file::memory:?cache=shared&_txlock=immediate")

But I think you are right. SQLite test is not the bottleneck of tests. So I will close this pull request.

[wxiaoguang]

And I think we already used :memory: in our unit test.

That's different. Other test uses the same connection pool.

But migration tests create 2 isolated connection pools, that's why it's difficult to play tricks with it.