faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
<FromGitter> <damianham> Granite question: I noticed n my server logs that every time a user field is updated the server first queries the database for the user by email address. I am sure this is due to the email validation that ensures the email is unique. I am updating a list of potentially thousands of users and I am modifying a field that holds an int and not the email address so there are potentially thousands of redundant select
<FromGitter> ... queries. I can work around this of course by updating the database directly but it would be better to handle such performance improvement in the ORM. IIRC Active record maintains a list of changed fields and only updates those fields that have been modified.
<FromGitter> <Blacksmoke16> iirc you can also do like `.save validate: false`
<FromGitter> <Blacksmoke16> but yes that would be more ideal, just needs someone to do it i guess
<FromGitter> <damianham> Thanks George I will try that
t1|Mike_ has joined #amber
t1|Mike has quit [Ping timeout: 276 seconds]
t1|Mike_ is now known as t1|Mike
test has joined #amber
test has quit [Client Quit]