Skip to content

Commit 59ffe51

Browse files
committed
Use LF line endings in readme.txt
1 parent 0602a2f commit 59ffe51

2 files changed

Lines changed: 53 additions & 56 deletions

File tree

.editorconfig

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,3 @@ indent_size = 2
1919

2020
[*.md]
2121
trim_trailing_whitespace = false
22-
23-
[{*.txt,wp-config-sample.php}]
24-
end_of_line = crlf
Lines changed: 53 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,53 @@
1-
=== SQLite Database Integration ===
2-
3-
Contributors: wordpressdotorg, aristath, janjakes, zieladam, berislav.grgicak, bpayton, zaerl
4-
Requires at least: 6.4
5-
Tested up to: 6.9
6-
Requires PHP: 7.2
7-
Stable tag: 2.2.21
8-
License: GPLv2 or later
9-
License URI: https://www.gnu.org/licenses/gpl-2.0.html
10-
Tags: performance, database
11-
12-
SQLite integration plugin by the WordPress Team.
13-
14-
== Description ==
15-
16-
The SQLite plugin is a community, feature plugin. The intent is to allow testing an SQLite integration with WordPress and gather feedback, with the goal of eventually landing it in WordPress core.
17-
18-
This feature plugin includes code from the PHPMyAdmin project (specifically parts of the PHPMyAdmin/sql-parser library), licensed under the GPL v2 or later. More info on the PHPMyAdmin/sql-parser library can be found on [GitHub](https://github.com/phpmyadmin/sql-parser).
19-
20-
== Frequently Asked Questions ==
21-
22-
= What is the purpose of this plugin? =
23-
24-
The primary purpose of the SQLite plugin is to allow testing the use of an SQLite database, with the goal to eventually land in WordPress core.
25-
26-
You can read the original proposal on the [Make blog](https://make.wordpress.org/core/2022/09/12/lets-make-wordpress-officially-support-sqlite/), as well as the [call for testing](https://make.wordpress.org/core/2022/12/20/help-us-test-the-sqlite-implementation/) for more context and useful information.
27-
28-
= Can I use this plugin on my production site? =
29-
30-
Per the primary purpose of the plugin (see above), it can mostly be considered a beta testing plugin. To a degree, it should be okay to use it in production. However, as with every plugin, you are doing so at your own risk.
31-
32-
= Where can I submit my plugin feedback? =
33-
34-
Feedback is encouraged and much appreciated, especially since this plugin is a future WordPress core feature. If you need help with troubleshooting or have a question, suggestions, or requests, you can [submit them as an issue in the SQLite GitHub repository](https://github.com/wordpress/sqlite-database-integration/issues/new).
35-
36-
= How can I contribute to the plugin? =
37-
38-
Contributions are always welcome! Learn more about how to get involved in the [Core Performance Team Handbook](https://make.wordpress.org/performance/handbook/get-involved/).
39-
40-
= Does this plugin change how WordPress queries are executed? =
41-
42-
The plugin replaces the default MySQL-based database layer with an
43-
SQLite-backed implementation. Core WordPress code continues to use
44-
the wpdb API, while queries are internally adapted to be compatible
45-
with SQLite syntax and behavior.
46-
47-
== Changelog ==
48-
49-
= 2.2.21 =
50-
51-
* Monorepo setup + release automation ([#334](https://github.com/WordPress/sqlite-database-integration/pull/334))
52-
* Rework release workflow ([#350](https://github.com/WordPress/sqlite-database-integration/pull/350))
53-
* Fix incorrect PHP polyfill implementations ([#338](https://github.com/WordPress/sqlite-database-integration/pull/338))
1+
=== SQLite Database Integration ===
2+
3+
Contributors: wordpressdotorg, aristath, janjakes, zieladam, berislav.grgicak, bpayton, zaerl
4+
Requires at least: 6.4
5+
Tested up to: 6.9
6+
Requires PHP: 7.2
7+
Stable tag: 2.2.21
8+
License: GPLv2 or later
9+
License URI: https://www.gnu.org/licenses/gpl-2.0.html
10+
Tags: performance, database
11+
12+
SQLite integration plugin by the WordPress Team.
13+
14+
== Description ==
15+
16+
The SQLite plugin is a community, feature plugin. The intent is to allow testing an SQLite integration with WordPress and gather feedback, with the goal of eventually landing it in WordPress core.
17+
18+
This feature plugin includes code from the PHPMyAdmin project (specifically parts of the PHPMyAdmin/sql-parser library), licensed under the GPL v2 or later. More info on the PHPMyAdmin/sql-parser library can be found on [GitHub](https://github.com/phpmyadmin/sql-parser).
19+
20+
== Frequently Asked Questions ==
21+
22+
= What is the purpose of this plugin? =
23+
24+
The primary purpose of the SQLite plugin is to allow testing the use of an SQLite database, with the goal to eventually land in WordPress core.
25+
26+
You can read the original proposal on the [Make blog](https://make.wordpress.org/core/2022/09/12/lets-make-wordpress-officially-support-sqlite/), as well as the [call for testing](https://make.wordpress.org/core/2022/12/20/help-us-test-the-sqlite-implementation/) for more context and useful information.
27+
28+
= Can I use this plugin on my production site? =
29+
30+
Per the primary purpose of the plugin (see above), it can mostly be considered a beta testing plugin. To a degree, it should be okay to use it in production. However, as with every plugin, you are doing so at your own risk.
31+
32+
= Where can I submit my plugin feedback? =
33+
34+
Feedback is encouraged and much appreciated, especially since this plugin is a future WordPress core feature. If you need help with troubleshooting or have a question, suggestions, or requests, you can [submit them as an issue in the SQLite GitHub repository](https://github.com/wordpress/sqlite-database-integration/issues/new).
35+
36+
= How can I contribute to the plugin? =
37+
38+
Contributions are always welcome! Learn more about how to get involved in the [Core Performance Team Handbook](https://make.wordpress.org/performance/handbook/get-involved/).
39+
40+
= Does this plugin change how WordPress queries are executed? =
41+
42+
The plugin replaces the default MySQL-based database layer with an
43+
SQLite-backed implementation. Core WordPress code continues to use
44+
the wpdb API, while queries are internally adapted to be compatible
45+
with SQLite syntax and behavior.
46+
47+
== Changelog ==
48+
49+
= 2.2.21 =
50+
51+
* Monorepo setup + release automation ([#334](https://github.com/WordPress/sqlite-database-integration/pull/334))
52+
* Rework release workflow ([#350](https://github.com/WordPress/sqlite-database-integration/pull/350))
53+
* Fix incorrect PHP polyfill implementations ([#338](https://github.com/WordPress/sqlite-database-integration/pull/338))

0 commit comments

Comments
 (0)