I'm curious how Netsuite does custom records and stuff. Like, on the database side, when I create a new custom record, does it create a new table or does it have some kind of generic

custom_record

table that stores the metadata and then some larger relational table

custom_record_data

that stores the data and the code itself manages the rendering of that data on the screen and stuff?

The internal ids of all custom record fields are all in the same collision space. I.e. if you have

customrecord_a

with a field

custrecord_field

, you cannot make

customrecord_b

with a field

custrecord_field

since that collides with the existing field belonging to

customrecord_a

Hopefully that provides some insight

@jkabot yeah, I get that. I'm just interested in how the software knows what each form looks like structurally. I doubt they're doing

CREATE TABLE

stuff. Since custom records have an internal id, my assumption is there is a generic

custom_record

table in which the metadata of that record is stored in json or xml format. Then another table for the metadata for the custom fields and then another table to store the data. Then the software is smart enough to render stuff based upon the metadata of the fields and stuff. The only question I have is if you store stuff like that, how in the WORLD can you have as fast of searching as what Netsuite provides? 🤯