Hey all again 👋 I have an aggregate

Hey all again

, I have an aggregate that get intilized by it's own id before being persisted to Convex. After many tries I kept hitting a validator error (the on the mutation). Eventually I just copied an the id of an existing record, deleted that record and tried using that Id, but I discovered that Convex ignored the

_id

_id

and inserted the document with another

_id

_id

. Is there is no way of assigning an Id to a record before

insert

insert

fawwazOP•8/2/23, 12:43 PM

this the code I have for the mutation, will ideal have

_id

_id

inside it already

sshader•8/2/23, 1:46 PM

There's currently no way of assigning an ID to a Document before

insert

insert

. IDs used in optimistic updates are essentially placeholders until

insert

insert

can assign a real ID (we may build a way to allocate IDs from the client in the future, but at the moment it's not supported).

Can you tell me more about your use case so we can brainstorm some alternatives? Where are you currently trying to assign the ID?

fawwazOP•8/2/23, 2:08 PM

Hey @sshader So I'm exploring apply DDD with Convex. What I'm trying to do is isolate the domain from the database implementation. so usually I start by defining the shape of my Aggregates which in a simple application will have mirror many the same properties as the Convex Model, including the

id

id

After that I have list of commands that take any depndecies that might need to do their work. For example I have a that will create the aggregate. Since the model definition including an Id a random will be assigned.

this is my current implementation for that command handler

of course I can change the modle shape for to have the

id

id

optional and this is what I'm currently doing, but that mean checking for if

id

id

exist in flows where I know an will most currently be there.

Not sure if I'm departing very far from how Convex should be used though

, tell me what you think?

sshader•8/2/23, 2:21 PM

Where does the ID come from when it is provided? Looks like doesn't provide an

_id

_id

but is written to expect an optional

_id

_id

?

Also a workaround is to define your own field (e.g.

id

id

) and an index to support fast look ups, and then you'd be able to control how that field gets populated (and essentially ignore the built in

_id

_id

field). But I'm still curious if there's a way we could support this with the built in field

fawwazOP•8/2/23, 2:23 PM

oh my applogies that was my current impemenation, here is the one I was trying to do before I discovred the issue with assigning Ids

so basically will check for id if non exist will add one

fawwazOP•8/2/23, 2:26 PM

hmm the approach of assigning my id does seem interesting , I might hit similar issues of needing to check for Convex

_id

_id

but will give it try

sshader•8/2/23, 2:46 PM

I think I'm still missing why needs an

_id

_id

at all vs. providing all the fields aside from

_id

_id

and

_creationTime

_creationTime

and always creating a new document using ?

fawwazOP•8/2/23, 2:50 PM

so is not concern where is it going to be used, it only guarantee that you will get a valid aggregate. For the inset flow the id might not be needed but for other flows it would be needed (eg handle model run result).