This HTML5 document contains 53 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n2http://dbpedia.org/resource/Hi/
dctermshttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
n18http://dbpedia.org/resource/File:
n19http://dbpedia.org/resource/%5D,_int%5D,_max_lo:_int_=_1000)_-%3E_None:
foafhttp://xmlns.com/foaf/0.1/
n15http://en.wikipedia.org/wiki/Hi/
n20https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
n16https://stackoverflow.com/questions/282099/
rdfshttp://www.w3.org/2000/01/rdf-schema#
n8http://commons.wikimedia.org/wiki/Special:FilePath/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n11https://vladmihalcea.com/the-hilo-algorithm/
dbchttp://dbpedia.org/resource/Category:
dbphttp://dbpedia.org/property/
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
n2:Lo_algorithm
rdfs:label
Hi/Lo algorithm
rdfs:comment
Hi/Lo is an algorithm and a key generation strategy used for generating unique keys for use in a database as a primary key. It uses a sequence-based hi-lo pattern to generate values. It can be used with domain-driven design (DDD). Hi/Lo is used in scenarios where an application needs its entities to have an identity prior to persistence. It is a value generation strategy. An alternative to Hi/Lo would be to generate keys as universally unique identifiers (UUID).
foaf:depiction
n8:Hilo_algorithm.svg
dcterms:subject
dbc:Object-relational_mapping dbc:Database_algorithms dbc:Articles_with_example_Python_(programming_language)_code dbc:Articles_with_example_pseudocode
dbo:wikiPageID
62235560
dbo:wikiPageRevisionID
1114594971
dbo:wikiPageWikiLink
dbr:Primary_key dbc:Object-relational_mapping dbr:Domain-driven_design dbr:Universally_unique_identifier dbr:Integer_(computer_science) dbc:Database_algorithms dbc:Articles_with_example_Python_(programming_language)_code dbr:Entity_Framework dbr:RavenDB dbr:Ruby_on_Rails dbr:NHibernate dbr:Hibernate_(framework) dbr:Doctrine_(PHP) dbr:Apache_Cayenne dbc:Articles_with_example_pseudocode dbr:Microsoft_SQL_Server dbr:Stored_procedure dbr:Python_(programming_language) dbr:PostgreSQL dbr:Distributed_transaction n18:Hilo_algorithm.svg n19:
dbo:wikiPageExternalLink
n11: n16:whats-the-hi-lo-algorithm
owl:sameAs
wikidata:Q85766448 n20:BudT3
dbp:wikiPageUsesTemplate
dbt:Var dbt:Database dbt:Reflist dbt:Quote
dbo:thumbnail
n8:Hilo_algorithm.svg?width=300
dbp:author
Onur Gumus and Mugilan T. S. Ragupathi Suhas Chatekar
dbp:source
Learning NHibernate 4 ASP.NET Core 2 Fundamentals
dbp:text
While auto incremented IDs are simpler, whenever you add an entity to the context, this addition forces the entity to be inserted to the database. That is because we can only retrieve the ID if the actual insertion happens in the case of auto incremented IDs. The HiLo algorithm frees us from this restriction by reserving the IDs beforehand using a database sequence. This implementation uses hi/lo algorithm to generate identifiers. Algorithm uses a high value retrieved from database and combines it with range of low values to generate a unique identifier. High value is from column of table by default. But you can override this to use a different table. This algorithm also supports specifying a parameter which can be used to retrieve high value for different entities from different rows of the table. hilo needs a set of two numbers to work with. One is hi which is sourced from a database table and other is lo which is calculated by NHibernate. NHibernate combines these two numbers using a formula to generate a unique number that can be used as identifier.
dbo:abstract
Hi/Lo is an algorithm and a key generation strategy used for generating unique keys for use in a database as a primary key. It uses a sequence-based hi-lo pattern to generate values. It can be used with domain-driven design (DDD). Hi/Lo is used in scenarios where an application needs its entities to have an identity prior to persistence. It is a value generation strategy. An alternative to Hi/Lo would be to generate keys as universally unique identifiers (UUID).
prov:wasDerivedFrom
n15:Lo_algorithm?oldid=1114594971&ns=0
dbo:wikiPageLength
10876
foaf:isPrimaryTopicOf
n15:Lo_algorithm
Subject Item
dbr:Hi-Lo
dbo:wikiPageWikiLink
n2:Lo_algorithm
Subject Item
n15:Lo_algorithm
foaf:primaryTopic
n2:Lo_algorithm