Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@devTea Im trying to do it but my SQL knowlage sucks really hard so that's annoying as living fuck to do ;-;
-
Literally every single ORM is damn near good for just CRUD shit. The problem most of us have with orms is using them for anything else.
The best way will always be making use of your own SQL, always -
-
You do not need an ORM, you need to learn your SQL correctly. ORM is not an excuse but a powerhouse of a tool which is not meant to be simple. Simple operations should be performed with SQL directly. A lot of people confuse ORM with "SQL to Object Magic", which it is not.
The image summarizes whether or not you need ORM and I use it for all my projects to determine if I start with or without it. But please git gud at SQL. -
@frickerg
for reference. This is INSERT syntax:
https://sqlite.org/lang_insert.html...
now, click all spoilers.
Yeah, I can get good. Just gimme few years or something.
But production must go on. And ORM, all things considered actually speed up writing of your code. If only there was simple one, that will still give acceleration in writing code while not making it X times slower. -
@DubbaThony your statement kinda shows that you are not aware what ORM is. It is not a simplified SQL syntax, therefore it wouldn't make sense to implement a "simple" ORM.
If you really want to have a simple SQL just check out Knex or other query builders rather than using a hammer and expect it to work like a shovel. -
@frickerg
As far as I can tell, anyone who starts with Querry builders end up using ORMs... -
Related Rants
Im fucking fed up with overbloated "all in one" ORMs.
For shit I cant find simple ORM that would literally just do fucking CRUD for me.
Thats all I require for some small project, yet still for few tables I have 2 choices:
a) do it without ORM and write models with raw SQL (which I usually end up doing, as its just more fault tolerant and works better)
b) install overloaded ORM that I wont use even 1% of features
Guys, why the fuck nobody created anything small, tiny and yet usefull? I know my SQL sucks and that is reason I want to use ORM in the first place. But when Im just forced?
Best what I found in terms of ease of use, and beeing not too heavy was RedBeanPHP.
A freaking ORM that will create database on the fly. It's awesome, sure. It's usefull, sure.
BUT STILL ALL I NEED IN SMALL PROJECT IS 1% OF THAT FUNCTIONALITY.
Does literally every single ORM dev want to feel their dick when they list out features list?
There should be allways proper tool for proper job. Its like using symfony for creating onepage website with contact form. WTF.
rant
library
orm
overbloated
php
code