Tyler W. Walch

> Thanks @tywalch. I was looking for a typecheck command to run. I've since found test:types. I will try to find some time to dig in deeper. This is an...

Hi @Talljoe 👋 You're right about hitting the case described in https://github.com/tywalch/electrodb/issues/366. You could take several directions here, but here's some background about what you see. There is a runtime...

I just tried this locally, with the latest version (`2.15.0`) like this, and everything worked as expected: https://gist.github.com/tywalch/fa43890fa0c7beb84804811b7f95bf46 You have the concept of "virtual columns" correct, and your implementation looks...

I am going to close this ticket, but feel free to reopen it if you need to pick this question back up 👍

Hi @raryanpur 👋 Thanks for posting! The philosophy of validation in the library has generally been to focus on verifying Electro specific conventions and then, for everything else, get out...

Hi @iOSonntag 👋 It sounds like you're you're reporting a two different issues: 1. The execution option `preserveBatchOrder` doesn't seem to be working as expected. 2. Order is not maintained...

Hi @zirkelc 👋 This is an improvement that has been considered (I thought there might have been an existing issue for this?), and it is an ideal state. I remember...

A quick flyby comment while I have a second, in case this might solve your need quickly: You can define a custom attribute (that's strongly typed) using this function: https://electrodb.dev/en/reference/typescript/#customattributetype...

If you're just using JavaScript, you can use the attribute type "any". Filtering with the "where" method will work on "any" attribute types.

Hi @raryanpur 👋 Thanks for submitting this! Ultimately the reason this validation exists on the attribute name (as opposed to the field) is because the attribute _name_ is what's used...