💾 Archived View for gmn.clttr.info › sources › gmnifaq.git › tree › data › data.sqlite.example captured on 2024-05-10 at 11:10:26. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
SQLite format 3 @ .K� j � Vv� �� {v��
�
z��� �w-�-triggerquestions_insertquestionsCREATE TRIGGER questions_insert AFTER INSERT ON questions FOR EACH ROW BEGIN INSERT INTO fts_data (q_id, text) VALUES (new.id, new.question);
INSERT INTO fts_data (q_id, text) VALUES (new.id, new.answer); END�%-� triggerquestions_updatequestionsCREATE TRIGGER questions_update AFTER UPDATE ON questions FOR EACH ROW BEGIN DELETE FROM fts_data WHERE q_id = old.id;
INSERT INTO fts_data (q_id, text) VALUES (new.id, new.question);
INSERT INTO fts_data (q_id, text) VALUES (new.id, new.answer); END�%-� triggerquestions_deletequestionsCREATE TRIGGER questions_delete AFTER DELETE ON questions FOR EACH ROW BEGIN DELETE FROM fts_data WHERE q_id = old.id; END�J#�gtriggertags_updatetagsCREATE TRIGGER tags_update AFTER UPDATE ON tags FOR EACH ROW BEGIN DELETE FROM fts_data WHERE t_id = old.id;
INSERT INTO fts_data (t_id, text) VALUES (new.id, new.name); END� #�mtriggertags_deletetagsCREATE TRIGGER tags_delete AFTER DELETE ON tags FOR EACH ROW BEGIN DELETE FROM fts_data WHERE t_id = old.id; END� #�triggertags_inserttagsCREATE TRIGGER tags_insert AFTER INSERT ON tags FOR EACH ROW BEGIN INSERT INTO fts_data (t_id, text) VALUES (new.id, new.name); ENDi++� tablefts_data_configfts_data_configCREATE TABLE 'fts_data_config'(k PRIMARY KEY, v) WITHOUT ROWIDm --� tablefts_data_docsizefts_data_docsize
CREATE TABLE 'fts_data_docsize'(id INTEGER PRIMARY KEY, sz BLOB)p--�tablefts_data_contentfts_data_content CREATE TABLE 'fts_data_content'(id INTEGER PRIMARY KEY, c0, c1, c2){%%�9tablefts_data_idxfts_data_idxCREATE TABLE 'fts_data_idx'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWIDg
''� tablefts_data_datafts_data_dataCREATE TABLE 'fts_data_data'(id INTEGER PRIMARY KEY, block BLOB)�))�Ktabletags_questionstags_questionsCREATE TABLE tags_questions (t_id INTEGER REFERENCES tags (id), q_id REFERENCES questions (id))� u �?tablefts_datafts_dataCREATE VIRTUAL TABLE fts_data
USING FTS5(t_id, q_id, text, tokenize = "porter unicode61")��QtablequestionsquestionsCREATE TABLE questions (id INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, question TEXT, answer TEXT)v�OtabletagstagsCREATE TABLE tags (id INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, name TEXT (30) UNIQUE NOT NULL)� h P++Ytablesqlite_sequencesqlite_sequenceCREATE TABLE sqlite_sequence(name,seq)� ' '; indexsqlite_autoindex_tags_1tags � �� gemini web � �� questionstags �
� �� �M ;�oCan i search in gemini?Of course! Although discoverability is not as a big deal as in the web (no SEO!) someone need to be able to find the things she/he is interested in.
There's the major search engine for gemini called GUS:
Additionally there's no geminispace.info, a capsule that uses the very same software as GUS - called GUS too:
Theres also a http mirror available at
https://gemini.circumlunar.space
But the truth is in the protocol._ ?�Whats wrong with the web?It's bloated, cookie banners everywhere, user tracking and so on.�s 5�AWhat is this gemini?Gemini is a new application-level internet protocol for the distribution of arbitrary files, with some special consideration for serving a lightweight hypertext format which facilitates linking between files. You may think of Gemini as "the web, stripped right back to its essence" or as "Gopher, souped up and modernised a little", depending upon your perspective. Gemini may be of interest to people who are:
Opposed to the web's ubiquitous user tracking
Tired of obnoxious adverts, autoplaying videos and other misfeatures
Interested in low-power computing and/or low-speed networks
Gemini is intended to be simple, but not necessarily as simple as possible. Instead, the design strives to maximise its "power to weight ratio", while keeping its weight within acceptable limits. Gemini is also intended to be very privacy conscious, to be difficult to extend in the future (so that it will stay simple and privacy conscious), and to be compatible with a "do it yourself" computing ethos. For this last reason, Gemini is technically very familiar and conservative: it's a protocol in the traditional client-server request-response paradigm, and is built on mature, standardised technology like URIs, MIME media types, and TLS.