The BsonTypeClassMap
to use with this record.
The BsonTypeClassMap
to use with this record.
Delete the instance from backing store
Find a single row by a qry using String key and Any value
Find a single document by a qry using a json value
Find a single row by a Long id
Find a single row by an Int id
Find a single row by a String id
Find a single row by a UUID
Find a single row by an ObjectId
Find a single row by a qry, using a Bson.
Find all documents using a k, v query with JOBject sort
Find all documents using a k, v query
Find all documents using a JObject query with sort
Find all documents using a JObject query
Find all documents using a Bson query with Bson sort
Find all documents using a Bson query.
Find all documents using a Bson query. These are for passing in regex queries.
Find all rows and retrieve only keys fields.
Find all rows and retrieve only keys fields.
Find all rows using a Bson query.
Find all rows in this collection.
Find all rows in this collection. Retrieves all documents and puts them in memory.
Find all documents with the given ids
Find a single row by Any This doesn't work as find because we need JObject's to be implicitly converted.
Insert multiple records
Check this record's fields and add any Codecs needed.
Check this record's fields and add any Codecs needed.
Save the instance in the appropriate backing store.
Use the collection associated with this Meta.
Use the collection associated with this Meta.
Use the db associated with this Meta.
Use the db associated with this Meta.
Create a BasicDBObject from the field names and values.
Create a BasicDBObject from the field names and values. - MongoFieldFlavor types (List) are converted to DBObjects using asDBObject
(Since version 3.4.3) RecordCodec is now used instead.
(Since version 3.4.3) RecordCodec is now used instead.
(Since version 3.4.3) Use createIndex that takes IndexOptions as argument instead
(Since version 3.4.3) Use deleteOne or deleteMany instead
(Since version 3.4.3) Use deleteOne or deleteMany instead
(Since version 3.4.3) Use deleteOne or deleteMany instead
Return the value of a field suitable to be put in a DBObject
Return the value of a field suitable to be put in a DBObject
(Since version 3.4.3) RecordCodec is now used instead.
Creates a new record, then sets the fields with the given DBObject.
Creates a new record, then sets the fields with the given DBObject.
- the DBObject
Box[BaseRecord]
(Since version 3.4.3) RecordCodec is now used instead.
(Since version 3.4.3) No longer supported. This will be removed in Lift 4.
Replaces document with new one with given id.
Replaces document with new one with given id. if upsert
is set to true inserts eqs
in similar way as save() from sync api.
(Since version 3.4.3) No longer supported. This will be removed in Lift 4.
Save a document to the db using the given Mongo instance
Save a document to the db using the given Mongo instance
(Since version 3.4.3) Set WriteConcern in MongoClientOptions or on this MongoMetaRecord
Save the instance in the appropriate backing store
Save the instance in the appropriate backing store
(Since version 3.4.3) Set WriteConcern in MongoClientOptions or on this MongoMetaRecord
(Since version 3.4.3) Use saveOperation instead
Populate the inst's fields with the values from a DBObject.
Populate the inst's fields with the values from a DBObject. Values are set using setFromAny passing it the DBObject returned from Mongo.
- the record that will be populated
- The DBObject
Unit
(Since version 3.4.3) RecordCodec is now used instead.
Update only the dirty fields.
Update only the dirty fields.
Note: PatternField will always set the dirty flag when set.
(Since version 3.4.3) Use updateOne, or replaceOne instead
Update a record with a DBObject query
Update a record with a DBObject query
(Since version 3.4.3) Use updateOne, or replaceOne instead
Update one record with a DBObject query
Update one record with a DBObject query
(Since version 3.4.3) Use updateOne, updateMany, or replaceOne instead
Update records with a JObject query
Update records with a JObject query
(Since version 3.4.3) Use updateOne, updateMany, or replaceOne instead
Update records with a JObject query using the given Mongo instance
Update records with a JObject query using the given Mongo instance
(Since version 3.4.3) Use updateOne, updateMany, or replaceOne instead
(Since version 3.4.3) Use updateOne or updateMany instead
(Since version 3.4.3) Use updateOne or updateMany instead
(Since version 3.4.3) Use updateOne or updateMany instead
Update multiple records with a DBObject query
Update multiple records with a DBObject query
(Since version 3.4.3) Use updateMany instead
Upsert records with a DBObject query
Upsert records with a DBObject query
(Since version 3.4.3) Use updateOne, updateMany, or replaceOne instead
(Since version 3.4.3) Use useCollection instead
(Since version 3.4.3) No longer supported. This will be removed in Lift 4.
(Since version 3.4.3) Use useDatabase instead