Difference between revisions of "Bigint field"

From EPrints Documentation
Jump to: navigation, search
(Additional Properties)
(Removed link to API page (just a redirect to this))
Line 25: Line 25:
 
Bigint fields are stored in the database as
 
Bigint fields are stored in the database as
 
  fieldname BIGINT(20)
 
  fieldname BIGINT(20)
 
== API ==
 
See [[API:EPrints/MetaField/Bigint|API page]].
 
  
 
== Examples ==
 
== Examples ==

Revision as of 09:39, 9 July 2024

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 store (i.e. greater than 2,147,483,647 or less than -2,147,483.647) in a standard database Int field.

Inheritance

Additional Properties

As for Int fields except for

Name Default Value Required Description Notes
digits 18 NO The maximum number of digits for the big integer value. Different from Int field default (9). Analogous to maxlength. Database BIGINT(20) cannot reliably store numbers that takes up more than 18 digits (including a sign if negative).

Required Phrases

No additional phrases beyond those required for Int fields.

Database

Bigint fields are stored in the database as

fieldname BIGINT(20)

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,
}