Bigint field: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
== Properties == | == Properties == | ||
As for [[Int field]]s except for: | |||
{| border="1" cellpadding="3" cellspacing="0" | {| border="1" cellpadding="3" cellspacing="0" | ||
| name || default || description | | name || default || description | ||
| Line 18: | Line 20: | ||
== Required Phrases == | == Required Phrases == | ||
No additional phrases. | No additional phrases beyond those required for [[Int field]]s. | ||
== Database == | == Database == | ||
Bigint fields are stored in the database as | |||
fieldname BIGINT(20) | fieldname BIGINT(20) | ||
Revision as of 08:36, 9 April 2023
EPrints 3 Reference: Directory Structure - Metadata Fields - Repository Configuration - XML Config Files - XML Export Format - EPrints data structure - Core API - Data Objects
Metadata Fields: Arclanguage - Base64 - Bigint - Boolean - Compound - Counter - Dataobjref - Date - Decimal - Email - Fields - Float - Id - Idci - Image - Int - Itemref - Keywords - Langid - Longtext - Longtext_counter - Multilang - Multipart - Name - Namedset - Pagerange - Recaptcha - Recaptcha3 - Relation - Search - Secret - Set - Storable - Subject - Subobject - Text - Time - Timestamp - Url - Uuid
Description
This field represents an integer whose value may be too big to to store in a standard database integer field.
Inheritance
Properties
As for Int fields except for:
| name | default | description |
| digits | n/a | This property is taken from the repository configuration. |
Required Phrases
No additional phrases beyond those required for Int fields.
Database
Bigint fields are stored in the database as
fieldname BIGINT(20)
API
See API page.
Examples
A basic example.
{
name => 'population',
type => 'bigint',
}
Restrict number of digits can be added to this field in the wokflow.
{
name => 'hesa_id',
type => 'bigint',
digits => 13,
}