upsert

I have a collections of documents in mongodb, with the expireAfterSeconds property set on a date-type index. For the sake of argument, the documents are set to expire after one hour. When I update a document in this collection, which one of the following will happen? a) The document will expire one hour after the original creation time. b) The document will expire one hour after the update time. c) The document will expire one hour after the indexed variable 's time, whatever that may be. d) None of the above I think that it's c , but cannot find the reference to confirm it. Am I correct?

I'm trying to implement your basic UPSERT functionality, but with a twist: sometimes I don't want to actually update an existing row. Essentially I'm trying to synchronize some data between different repositories, and an Upsert function seemed like the way to go. So based largely on Sam Saffron's answer to this question , as well as some other research and reading, I came up with this stored procedure: (note: I'm using MS SQL Server 2005, so the MERGE statement isn't an option) CREATE PROCEDURE [dbo].[usp_UpsertItem] -- Add the parameters for the stored procedure here @pContentID varchar(30) =

In this post, the accepted answer explains that you cannot have the same fields under $set and $setOnInsert in an upsert operation. Can someone explain why this is? It seems like the $setOnInsert shouldn't conflict with $set , since the former is used when a document is inserted, and the latter is used when the document is updated. $set operator is used on upsert too. So it's nonsense to refer same fields both on $set and $setOnInsert . Just try this on an empty collection: db.items.remove(); db.items.update({},{$set:{a:1},$setOnInsert:{b:2}},{upsert:1}) db.items.find({}); 来源： https:/

I am trying to perform an UPSERT in PostgreSQL using the jOOQ library. For doing this I am currently trying to implement the following SQL statement in jOOQ: https://stackoverflow.com/a/6527838 My code looks like this so far: public class UpsertExecutor { private static final Logger logger = LoggerFactory.getLogger(UpsertExecutor.class); private final JOOQContextProvider jooqProvider; @Inject public UpsertExecutor(JOOQContextProvider jooqProvider) { Preconditions.checkNotNull(jooqProvider); this.jooqProvider = jooqProvider; } @Transactional public <T extends Record> void executeUpsert(Table<T>

I need to write a row to the database regardless of whether it already exists or not. Before using NHibernate this was done with a stored procedure. The procedure would attempt an update and if no rows were modified it would fallback to an insert. This worked well because the application doesn't care if the record exists. With NHibernate, the solutions I have found require loading the entity and modifying it, or deleting the entity so the new one can be inserted. The application does have to care if the record already exists. Is there a way around that? Does the Id Matter? Assigned Id The

Using Postgres 9.6, I have followed the strategy recommended in https://stackoverflow.com/a/40325406/435563 to do an INSERT or SELECT and return the resulting id: with ins as ( insert into prop (prop_type, norm, hash, symbols) values ( $1, $2, $3, $4 ) on conflict (hash) do update set prop_type = 'jargon' where false returning id) select id from ins union all select id from prop where hash = $3 However, sometimes this returns nothing. I would have expected it to return a row no matter what. How can I fix it to insure it always returns an id? NB, despite not returning a row, the row does seem

I'm writing an application that sync's entities from a third party datasource into our own schema, with a transformation/mapping step in between. I'm using Hibernate to represent and persist the entities in our own schema. A problem I'm running into is that I have a unique multi-column key on one of my tables. The behavior I would like to see is analogous to an upsert: when Hibernate goes to persist an entity and detects a unique constraint violation, it does an update instead. We are using MySQL, which provides an INSERT ... ON DUPLICATE KEY UPDATE syntax, but I'm not sure how or if Hibernate