Fieldpine Logo Documentation Home  
POS Commands Home

The storage command has a very large collection of functions covering normal record reading and writing, and also metadata and control functionality.

While this is documented as a seperate command it is always reached through the storage(function(...)) command

Commnd Overview

internal(...)
Internal functions generally relating to metadata. Internal commands should typically not be used for general retailing operation, instead reserved for support functions.
query(%s)
close(%s)
open(%s)
store(%s)
isfield(%s)
delete(%s)
fetch(%s)
next(%s)
update(%s)
transfer(%s)
backup(%s)
compress
online
offline
journal(%s)
fdldb(%s)
sql(%s)
addrow(%s)
indexcheck(...)
(19 Sep 2012, P1726) Verify key indexes exist on tables. The following keywords are possible.

This command is commonly accessed by quickcode 71242 which checks the indexes. Or quickcode 71353 which checks the indexes and attempts to add any required.

Examples:

storage(indexcheck(major))
storage(indexcheck(major,add,silent))

physkey(...)
(8 May 2013) Manage physkey fields on tables. This command can be extremely dangerous when executed in a multi store environment. There are two main forms of this command

The physkey field can be considered a globally unique primary key, albeit one that can be generated without central coordination. It is similar to a GUID or UUID, but the internal structure is slightly more index friendly than random values. See about physkeys for more details

renumber(%s)