<FromGitter>
<eliasjpr> But why you cannot annotate the macros?
<FromGitter>
<Blacksmoke16> because the macro just adds stuff to a constant that later on creates the properties
<FromGitter>
<Blacksmoke16> vs having the macro define the property
<FromGitter>
<Blacksmoke16> ideally we would refactor the macro to just use annotations under the hood and remove all the mutable constant stuff
<FromGitter>
<Blacksmoke16> is going to take some work but should be doable
<FromGitter>
<eliasjpr> Which gets processed first annotations or macro?
<FromGitter>
<Blacksmoke16> well you access annotations within macros
<FromGitter>
<Blacksmoke16> so at compile time, it would build out your array of values etc
<FromGitter>
<Blacksmoke16> by pulling properties with the annotation
<FromGitter>
<Blacksmoke16> i have a working prototype
<FromGitter>
<eliasjpr> Got it
_whitelogger has joined #amber
_whitelogger has joined #amber
<FromGitter>
<damianham> > behind the scenes would execute like `SELECT exists(SELECT 1 FROM listing_items WHERE id = $1);` ⏎ ⏎ Don't Foreign key constraints in database engines already handle this ?
<FromGitter>
<Blacksmoke16> Yes, but only when you go to save it
<FromGitter>
<Blacksmoke16> This way it never gets to my controller code
<FromGitter>
<Blacksmoke16> be much more painful to have begin/rescue everywhere to catch/throw a proper error everywhere it could happen
<FromGitter>
<Blacksmoke16> esp when that query takes like 0.05ms