⧼vector-jumptocontent⧽

Bigint field: Difference between revisions

From EPrints Documentation
Removed link to API page (just a redirect to this)
Actually leave in as should become available
 
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 ==

Latest revision as of 09:46, 9 July 2024


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)

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