⧼vector-jumptocontent⧽

Bigint field: Difference between revisions

From EPrints Documentation
Spacing after ToC
Moved description to top. Added link to API page.
Line 1: Line 1:
{{fieldtypes}}
{{fieldtypes}}


== Description ==
This field represents an integer whose value may be too big to to store in a standard database integer field.


== Inheritance ==
== Inheritance ==
* [[Metadata]]
* [[Metadata]]
** [[Int field]]
** [[Int field]]
*** [[Bigint field]]
*** [[Bigint field]]
== Description ==
This field represents an integer whose value may be too big to to store in a standard database integer field.


== Properties ==
== Properties ==
{| border="1" cellpadding="3" cellspacing="0"
{| border="1" cellpadding="3" cellspacing="0"
| name || default || description  
| name || default || description  
Line 23: Line 20:


== Database ==
== Database ==
Counter fields are stored in the database as
Counter fields are stored in the database as


Line 29: Line 25:


== API ==
== API ==
''To be added''
See [[API:EPrints/MetaField/Bigint|API page]].


== Examples ==
== Examples ==

Revision as of 08:15, 21 March 2023

Description

This field represents an integer whose value may be too big to to store in a standard database integer field.

Inheritance

Properties

name default description
digits n/a This property is taken from the repository configuration.

Required Phrases

No additional phrases.

Database

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