2646bc2db8
Showing how we can remove services, preventing cyclic imports and lessing the number of imports. Now db is in models. Db and models are highly tightened, according to go standards, you should put them in the same package. In models, there are folders separating the different methods used to modify the models. For example, if you want to create a user, you have to use /models (for the user struct) and /models/user (for creating a user. However, if you want to delete a torrent, you just have to import /models and do torrent.Delete(definitely bool). By the way packages in models are the plural name of a model. For example, you have torrent.go for a torrent model and its package torrents for db stuff related functions (Find, Create, Some helpers)
27 lignes
781 o
Go
27 lignes
781 o
Go
package models
|
|
|
|
import "time"
|
|
|
|
// OldComment model from old nyaa
|
|
type OldComment struct {
|
|
TorrentID uint `gorm:"column:torrent_id"`
|
|
Username string `gorm:"column:username"`
|
|
Content string `gorm:"column:content"`
|
|
Date time.Time `gorm:"column:date"`
|
|
|
|
Torrent *Torrent `gorm:"ForeignKey:torrent_id"`
|
|
}
|
|
|
|
// Size : Returns the total size of memory recursively allocated for this struct
|
|
func (c OldComment) Size() int {
|
|
return (1 + 2*2 + len(c.Username) + len(c.Content) + 3 + 1) * 8
|
|
}
|
|
|
|
// TableName : Return the name of OldComment table
|
|
func (c OldComment) TableName() string {
|
|
// cba to rename this in the db
|
|
// TODO: Update database schema to fix this hack
|
|
// I find this odd considering how often the schema changes already
|
|
return "comments_old"
|
|
}
|