Re: [rdf4j-dev] potential iterator leak in repository handling?

[Matthew Nguyen <nguyenm9@xxxxxxx>]

But what's the advantage of forcing models through a different triples interface than others? Seems simpler to treat all triples fetch the same no?

Unless models data is calculated on the fly, there's an expectation that it's persisted or loaded from somewhere which has potential baggage. 

On Thursday, April 6, 2023 at 06:38:36 PM EDT, Jeen Broekstra <jeen@xxxxxxxxxxxx> wrote:

On Thu, 6 Apr 2023, at 20:53, Matthew Nguyen via rdf4j-dev wrote:

I mean where does/should the data for models come from if not backed by a db?

The same place the data in any ArrayList comes from: it comes from whatever source you as a developer use to fill it. There is no "backing by a database" involved in the standard Model implementations in RDF4J - they are just passive in-memory data structures.

Perhaps Halyard is using some custom implementation of the Model interface? If so that could be causing the confusion here.

Jeen

PS I told a small lie I just realized: there is one implementation of the Model API that is backed by a database in RDF4J: the SailModel class. But it's for internal use only (mainly because it's not a recommended abstraction pattern, and prone to memory leaks if not used correctly) and not intended for use by third parties.

_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev