Programmer Humor

32555 readers

497 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

690

Sounds great in theory (programming.dev)

submitted 1 year ago by gogosempai@programming.dev to c/programmerhumor@lemmy.ml

71 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] mr_tyler_durden@lemmy.world 4 points 1 year ago

I much prefer having an in-memory database than mock what a database does.

Which sounds great in theory but then you get to find where your prod DB and testing DB differ and you have to keep chasing that. Unless you are using something like SQLite which has both (disk and in-memory) as an option.

I worked at a place that used a different in-memory DB (H2, IIRC) in place of our MySQL DB for testing. It ended up being hell to maintain and had to have hacks for how H2 and MySQL differ (tests would work in H2 but fail if run against MySQL or vice versa).