Difference between revisions of "Bigint field"

From EPrints Documentation
Jump to: navigation, search
m (Additional Properties)
(Additional Properties)
Line 11: Line 11:
  
 
== Additional Properties ==
 
== Additional Properties ==
As for [[Int_field#Additional Properties|Int fields]] except for:
+
As for [[Int_field#Additional Properties|Int fields]].
 
 
{| border="1" cellpadding="3" cellspacing="0"
 
| name || default || description
 
|-
 
| '''digits''' || n/a || '''This property is taken from the repository configuration.'''
 
|}
 
  
 
== Required Phrases ==
 
== Required Phrases ==

Revision as of 13:58, 11 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 Int field.

Inheritance

Additional Properties

As for Int fields.

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