DTSRAPI(3)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

okay so bestie, you're looking at DtSrAPI, and it's a library call page β€” the manual entry that describes the overview, constants, and structures for the DtSearch online API. Buckle up, because this is part 1 and it's giving reference material in the best way πŸ’…


✨ NAME ✨

DtSrAPI β€” describes overview, constants, and structures for DtSearch online API. periodt.


πŸ’– DESCRIPTION πŸ’–

The DtSearch API gives you programmatic access to the DtSearch search and retrieval engine. The API functions live in the library libDtSr, and they're directly linked into user-written search programs. no cap.

Search and retrieval of DtSearch databases is available through three essential API functions:

  • DtSearchInit β€” opens databases and other files, and generally initializes the search engine for subsequent requests. it's the setup bestie πŸŽ€
  • DtSearchQuery β€” is passed a user query and some search options, performs the requested search, and returns a linked list of structures called a results list, representing the objects satisfying the search. The results list contains abstracted information about the documents suitable for display to an end user, as well as private information used for subsequent retrievals. main character energy fr fr πŸ”₯
  • DtSearchRetrieve β€” retrieves an object given data from a results list node. When a results list contains all the information an application needs, retrieval by DtSearch may not be required. For example, when the documents themselves are not stored in DtSearch databases and the document references are available from the results list, the calling program may access the objects directly. lowkey convenient πŸ’…

🌸 DtSearch MessageList 🌸

All functions can potentially return multiple messages on a global linked list of messages called the MessageList. Most unsuccessful return codes append at least one message to the MessageList, but even successful returns may append messages, and multiple messages are always possible. so don't assume silence means perfection, bestie 😭

Messages are standard C text strings terminated by a zero byte, and were designed to be displayed directly to users. cute and functional πŸŽ€

Several API utility functions are available for manipulating the MessageList.

πŸ¦‹ Fatal API Errors πŸ¦‹

Certain fatal errors will require an immediate abort from the engine. By default, fatal error messages will be written to the stderr, but can be written to a text file specified in DtSearchInit. highkey important 🚨

All API aborts are implemented through a call to DtSearchExit. DtSearchExit() ensures cleanup of a number of system resources before the final call to exit. Developers can add an additional user exit to DtSearchExit to specify additional emergency clean up before process exit. the way that's both iconic and terrifying 🫢


πŸ‘‘ CONSTANTS πŸ‘‘

πŸ’œ Function Return Code Constants πŸ’œ

Most API functions return one of a set of standard integer return codes. The return code DtSrOK means complete success; other return codes indicate various levels of negative results or failure. vibe check on every return, bestie ✨

  • DtSrOK β€” normal, affirmative, successful response. slay πŸ’–
  • DtSrNOTAVAIL β€” generic negative response. For example, no hits on search, no such record, etc. it's giving "nothing here" 🫠
  • DtSrFAIL β€” miscellaneous unsuccessful engine returns. not the moment 😭
  • DtSrREINIT β€” engine reinitialized, request canceled. Often returned when invalid database name detected. Caller should clean up and call DtSearchReinit(). okay so reset era πŸ”„
  • DtSrERROR β€” fatal caller programming error. bestie, that's on you πŸ’€
  • DtSrABORT β€” fatal engine failure, caller must abort. no cap, this one's serious 🚨

🌈 Language Numbers 🌈

Each DtSearch database is associated with an integer representing, among other things, the natural language of its documents. These constants are used throughout the API to identify the supported languages. iykyk 🌍

  • DtSrLaENG β€” 0 β€” English, ASCII char set (default)
  • DtSrLaENG2 β€” 1 β€” English, ISO Latin-1 char set
  • DtSrLaESP β€” 2 β€” Spanish, ISO Latin-1 char set
  • DtSrLaFRA β€” 3 β€” French, ISO Latin-1 char set
  • DtSrLaITA β€” 4 β€” Italian, ISO Latin-1 char set
  • DtSrLaDEU β€” 5 β€” German, ISO Latin-1 char set
  • DtSrLaJPN β€” 6 β€” Japanese, EUC, auto kanji compounds
  • DtSrLaJPN2 β€” 7 β€” Japanese, EUC, listed kanji compounds
  • DtSrLaLAST β€” 7 β€” last supported DtSrLa constant

⭐ Other General Constants ⭐

  • DtSrVERSION β€” DtSearch version number string. the flex πŸ’…
  • DtSrMAX_KTNAME β€” maximum string length of a keytype name.
  • DtSrMAX_DB_KEYSIZE β€” maximum size of the unique document key.
  • DtSrMAXWIDTH_HWORD β€” largest possible word or stem size.
  • DtSrMAX_STEMCOUNT β€” maximum number of boolean search terms.

πŸŽ€ DtSrObjdate Type πŸŽ€

DtSrObjdate is a typdef (yes, that's the exact spelling in the source, bestie β€” not me 😭) for an unsigned integer used as a date/time stamp for documents.

DtSearch queries may be qualified by document date ranges. The data type packs certain standard struct tm fields into bitmap fields to minimize space. efficient queen πŸ‘‘

DtSrObjdate are based on the western Gregorian calendar and are not guaranteed to map to other time locales. so like, calendar behavior is not universal, noted πŸ—“οΈ

DtSearch objdates have a range from 1900 to 5995 inclusive and a resolution of 1 minute. From hi order bits to low:

  • 12 bits = tm_year β€” (0 - 4095, years since 1900 (1900 - 5995))
  • 4 bits = tm_mon β€” (0 - 11, month name index)
  • 5 bits = tm_mday β€” (1 - 31, day of month)
  • 5 bits = tm_hour β€” (0 - 23, hours since midnight)
  • 6 bits = tm_min β€” (0 - 59, minutes since top of hour)

πŸ’– STRUCTURES πŸ’–

okay bestie, this is where the actual data shapes live β€” the little structs that carry all the search tea β˜•βœ¨

πŸŽ€ DtSrKeytype Type πŸŽ€

       typedef struct {
           char        is_selected;
           char        ktchar;
           char        name   [ DtSrMAX_KTNAME+1];
       }       DtSrKeytype;

A DtSearch keytype references a logical subset of the database. periodt.

The primary identifier for a keytype is the keytype character ktchar. The ktchar identifies the subset of the database that has that character as the first character of its document keys.

The DtSrKeytype structure associates the ktchar with a short name string for use in user GUI labels identifying the keytype, and provides a boolean selection toggle for the keytype. cute little label-maker energy πŸ’…

An array of DtSrKeytype structures is maintained by the API for each database after API initialization. The API function DgSearchGetKeytypes() is used to access the array.

The is_selected boolean in each array node indicates whether the user has selected that keytype to be returned in the current search. The application must ensure that the boolean reflects the current state of the user's desires prior to any search. Typically this is done by having the keytypes array track user interface toggle buttons for the database. so like… keep the toggles in sync, bestie 😭

✨ DtSrResult Structure ✨

       typedef struct _DtSrResult {
           struct _DtSrResult *link;
           long        flags;
           long        objflags;
           long        objuflags;
           long        objsize;
           DtSrObjdates         objdate;
           short       objtype;
           short       objcost;
           int         dbn;
           DB_ADDR     dba;
           short       language;
           char        reckey [DtSrMAX_DB_KEYSIZE];
           int         proximity;
           char        *abstractp;
       }       DtSrResult;

The API function DtSearchQuery returns a results list upon successful completion of a search. A results list is a linked list of DtSrResult structures, where each node represents a database document that satisfied the query. linked-list realness πŸ”₯

  • link β€” Pointer to the next results list node.
  • flags β€” (reserved)
  • objflags β€” The constant DtSrFlNOTAVAIL means that the object is not retrievable from the search engine.
  • objuflags β€” User flags from database record. These are not used by DtSearch and are available for application definition.
  • objsize β€” In uncompressed bytes.
  • objdate β€” Zero is the null date; document is 'undated'.
  • objtype β€” Document type from database header record. Objtype is typically used by application code to identify and launch browsers.

Values above x1000 (4096) are set aside for application definition. The following constants identify defined values:

  • DtSrObjUNKNOWN β€” Document type unknown or not applicable
  • DtSrObjTEXT β€” Generic, unformatted flat text
  • DtSrObjBINARY β€” Generic binary object
  • DtSrObjSGML β€” Generic SGML formatted document
  • DtSrObjHTML β€” HTML formatted document
  • DtSrObjPOSTSCR β€” Postscript document
  • DtSrObjINTERLF β€” Interleaf document
  • DtSrObjDTINFO β€” DtInfo document
  • objcost β€” (reserved)
  • dbn β€” Database number; index into dbnames array from DtSearchInit and DtSearchReinit.
  • dba β€” Atomic document identifier within a database.
  • language β€” Language number of the database DtSrLa... constant).
  • reckey β€” Document's unique database key. The first character of reckey is the keytype character.
  • proximity β€” Sort field for ranking results lists. Derived from frequency of occurrence statistics for the query words in the document. Often displayed to users as the subjective 'distance' between the document and the query, in other words a measure of the likelihood that the document will satisfy the user's needs.
  • abstractp β€” Document's abstract string from the database.

ngl this struct is giving β€œmain character energy” β€” it carries the whole search result on its back 🫢

πŸ¦‹ DtSrHitword Structure πŸ¦‹

       typedef struct {
           long        offset; /* word location in cleartext */
           long        length; /* length of word */
       }       DtSrHitword;

Given a text string and the array of search terms returned from DtSearchQuery, DtSearchHighlight will generate a table of offsets and lengths where the search terms are located in the text. The table is typically used to highlight the search terms in the text in a manner appropriate to the application's user interface.

The DtSrHitword structure is one element in the table. For each search term to be highlighted, offset specifies the beginning byte for the term, and length specifies the extent of the term in bytes. highlighting slay ✨


🌈 SEE ALSO 🌈


okay bestie, that's the whole page πŸ’– the footer on this one is DtSrAPI(library call) β€” and there's no date listed, so she's timeless like a little Unix ghost πŸŽ€βœ¨. now go forth and highlight those hitwords, fr fr πŸ’…

πŸ“¦ where this page comes from