HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jinzhu
gorm
Go2013–2019
jinzhu / gorm

gorm

GORM V1, V2 moved to https://github.com/go-gorm/gorm

19Distinct people
23Mentions
0Explicit recommenders
657GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

GORM V1, V2 moved to https://github.com/go-gorm/gorm

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:59:04 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year23 dated mentions

Observed mentions: 2013-10-28 02:25:18 UTC to 2019-02-08 09:36:47 UTC.

02468102013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC110
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC303
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC909
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC303
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC404
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
GORM GORM V2 moved to https://github.com/go-gorm/gorm GORM V1 Doc https://v1.gorm.io/
Read the full README on GitHub

What Hacker News says

9 sources
I want to see the Go community and it's libraries flourish. But having libraries like this around which provide extra confusing and probably poorly maintained choices for users is detrimental to it's overall health. There's already great examples of maintenance rot found even amongst the very popular libraries like go-yaml and httprouter. One thing you can say about Go is it has 1000 Micro-frameworks, ORMs, Routers, and Logging libraries. Most of them are within a percent of giving the exact same feature set with the exact same approach and and ever so slightly different API. Lots of them share the same mistakes as they are a user's first project or a learning arena (though routing has been a pretty benchmarked area so that's been better than the others). As someone who has open source libraries, and who uses Go in their day job and at ho
Read the rest
me my personal opinion is that Go needs fewer, stronger libraries. Well supported, well maintained pieces rather than this illusion of choice that's presented today. I'm sorry if I came off as crass in my reply to the OP but that's simply the state I see in the community today. Ideally there'd be 2-4 ORMs in Go that would be the goto. And half would use a code-generation approach, half would use the reflection based approach. https://github.com/astaxie/beego/tree/master/orm https://github.com/cosiner/gomodel https://github.com/jinzhu/gorm https://github.com/go-gorp/gorp https://github.com/coocood/qbs https://github.com/go-reform/reform https://github.com/vattle/sqlboiler https://github.com/upper/db https://github.com/astaxie/beedb https://github.com/naoina/genmai https://github.com/monochromegane/argen https://github.com/square/squalor https://github.com/theduke/go-dukedb https://github.com/dropbox/godropbox/tree/master/database/sq... (...and more) And now: https://github.com/samonzeweb/godb Do we truly need this? This one in particular feels a lot like upperdb. And if it's for learning only, don't publish it to things like hackers news which makes people seem like it's something you should use as opposed to the more mature libraries out there. This is what I meant by fragmentation, it's an illusion of choice. There are actually very few logging/routing/orm/micro-framework libraries you should really use if you're serious about a project.
In Show HN: Godb is a simple Go ORM for PostgreSQL, MySQL, SQLite and SQL Server
Like you describe in the book, I had written a web-app in Go in which I was doing all the SQL handling manually, I found that it became very difficult to maintain this over time as I added new columns and more tables. Just the other day I switched to using GORM (github.com/jinzhu/gorm) for my database drivers and so far it's been a life-saver. Since this is a book about not using frameworks, GORM might be overkill for what you want to do, but I thought it was worth mentioning.
In Show HN: Book about writing web apps in Go without a framework
Not including an ORM layer does not decrease "value" of this framework, because you can attach such lib on your own. In Go the you are very flexible to set up a "a place where data will be stored/queried" - there is fabulous database/sql (or additional layers like lib/pq [1]) which is great for many use cases; also orm-like solutions like gocraft/dbr [2]; oh, I also should mention Gorm [3] or Bolt [4]. Setting them up is really easy in any Go web frameworks because (almost) all database modules rely on abstraction from stdlib. [1] https://github.com/lib/pq [2] https://github.com/gocraft/dbr [3] https://github.com/jinzhu/gorm [4] https://github.com/boltdb/bolt
In Iris: Fast back-end web framework for Go
RoR is an awesome framework that has (almost) everything you need to build monolithic web apps. Go is a different story. You need to join the pieces together to make something functional. You will probably need: - A router like [Gin](https://github.com/gin-gonic/gin) - A [XSRF token generator and validator](https://github.com/golang/net/blob/master/xsrftoken/xsrf.go) - An ORM like [Gorm](https://github.com/jinzhu/gorm) or [XORM](https://github.com/go-xorm/xorm) - A template lib like the one that comes with the stdlib - Node for front-end (ugh, this is the harder part) - The testing library in stdlib plus maybe [testify](https://github.com/stretchr/testify) - etc... Many nice things are missing. Some were [shamelessy copied by other people](https://github.com/go-testfixtures/testfixtures). Some you may need to implement yourself. The big a
Read the rest
dvantages is that Go has much better performance, and run on Windows, etc.
In Go best practices, six years in
Neat idea, thanks for posting this! I readily admit I'm absolutely guilty of implementing this sort pattern repeatedly across many go apps, and haven't ever [yet] gotten to making a generic implementation :) Some interesting notes (with a few curiosities): * This reminds me a lot of how jinzhu implemented the gorm [0] callbacks system. * The triggering is all global rather than per-instance (you can't create a new "trigger" struct). I wonder why this pattern was selected rather than allowing more fine-grained control and groups via instances. * Looking at the open PRs, #1 [1] was a surprise: Adding multiple listeners to one event enhancement Does go-trigger really not support multiple subscribers to an event? I wonder why it wasn't architected that way from the start. [0] https://github.com/jinzhu/gorm [1] https://github.com/sadlil
Read the rest
In Go-trigger

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.