Emmanuel
Emmanuel
@rodrigodagostino Haha, no, no worries mate. In fact I would say your argument made me rethink some of my implementations so that's a plus! Good find on the related issue....
I don't understand why this has been moved to the public roadmap's backlog when there is a fix already identified by community users. Unless there's some complexity I am not...
> the patch is no longer working for the current `drizzle-kit` version and i've spent too much time trying to update the patch without luck. instead i'm resulting to change...
> > Hmmm, the patch seems to work on my side. > > are you using `[email protected]`? most of the code was moved to `util.js` and there are pretty significant...
There very well could be some complexity to this issue that is being overlooked by discussions in this thread while being silently acknowledged by the core team (things like ensuring...
> I'm not sure you're correct here as there have been numerous patches submitted to resolve this issue As far as i know, there was only a single patch proposed...
@ArnaudD, what version of `drizzle-kit` are you using? Generating migrations with `0.19.13` and your workaround appears to results in an invalid quoted column type: ```sql CREATE TABLE IF NOT EXISTS...
@mislam, A guess would be that, in relation to [this discord post](https://discord.com/channels/1043890932593987624/1101108758127591435/1209557821545390110), some internal revisions are most-likely being made to better support addition of new features like generated columns (e.g....
While `.returns()` can help circumvent the current flaws stemming from the unknown cardinality of tables' relationships, it throws out any typing already inferred by the query's string and requires us...
I second this, having it on google fonts would be a blessing (plus it could let more designers know about it as another well-built free geometric sans font, which is...