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
-
@apex it is still better than storing JSON as nvarchar(MAX) which was my case :/
-
@gitpush Oh yeah, of course it's better!
Are you updating a legacy system? Or why do they asked you that? -
@apex it was a new system I was asked to build, so when I was explaining why I need x amount of time, GM just said: use json and you'll cut half the time
-
@gitpush Pretty solid arguments I'd say, perfect 5 out of 7.
-
@apex then say hello to hell of data querying. every time I wanted to dig up something in that JSON data, I end up using "LIKE" and waiting for a long time for it to finish rather than just hitting an '=' and do proper indexing
-
@gitpush Oh God, that's awful, but well, you can justify the querying timings with a paper where you explain that it's an implementation issue and put who said you should do it that way.
You know, just in case they try to throw shit at you. -
@apex I did justify it, but it was part of my resignation email lol
-
@gitpush Better leave before the shitstorm xD
-
@apex exactly :D
Store POJOs as json inside a database column so that we have a dynamic relational database!
For those who don't know what a POJO
*POJO: plain old Java object
Technically I was asked to store all data models as json in a single column 🙄
undefined
wk66