database design - What would be the advantages/disadvantages of prefixing column names with the item name? -

-

i working on blog module use in future project.

i decided prefix table names blog_ since it's module , different modules can have tables same name.

yesterday looking source code of ips boards , saw this. point interested me used prefixes column names too.

as example:

blog_categories     category_id     category_name     category_slug

or

blog_categories     id     name     slug

which 1 think better if it?

to extent flamewar territory, post discuss why think people choose 1 or other. in latter category. note pros , cons depend on database system.

reasons add prefixes

with prefixes, column names largely semantically unique. category_id refers id of category table. people think easier read. others point out allows joins use using () since means join columns have same name.

unfortunately latter case not perfect. using () limits planner can join since re-ordering joins can change join criteria. planners might able around however. check database documentation details.

reasons not add prefixes

i prefer not add prefixes. in model, columns logically bound primary key of table, using table namespace works allows simpler, more consistent naming regarding significance within table. numeric surrogate key example might called id while other columns may have other names.

part of preference may related choice of database. postgresql doesn't make hard distinction (the way innodb does) regarding primary key vs not null unique constraints. therefore find naming surrogate keys consistently nice, particularly when try designate natural primary keys. approach not work on database systems.


Comments

Post a Comment

Popular posts from this blog

Django REST Framework perform_create: You cannot call `.save()` after accessing `serializer.data` -

-
i have following viewset: class artistprofileviewset(viewsets.modelviewset): queryset = artistprofile.objects.all() serializer_class = artistprofileserializer def perform_create(self, serializer): if serializer.is_valid(): serializer.save() with following serializers: class simpleartisttrackserializer(serializers.hyperlinkedmodelserializer): class meta: model = artisttrack fields = (...my fields...) class artistprofileserializer(serializers.hyperlinkedmodelserializer): owners = userserializer(many=true, required=false) tracks = simpleartisttrackserializer(many=true, required=false) class meta: model = artistprofile fields = (...my fields...) i getting following error: assertionerror: cannot call `.save()` after accessing `serializer.data`.if need access data before committing database inspect 'serializer.validated_data' instead. i don't see editing serializer.data object. th...
Read more

Why does Go error when trying to marshal this JSON? -

-
i'm trying rather simple example of trying decode json file structs using golang. however, when attempting error that json: cannot unmarshal object go value of type []main.track which don't understand. here's code in question, , json can found here . package main import ( "encoding/json" "fmt" "net/http" "os" ) // tracks group of track types type tracks struct { tracks []track } // track represents singular track type track struct { name string url string artist artist } // artist represents single artist type artist struct { name string mbid string url string } func main() { url := "http://ws.audioscrobbler.com/2.0/?method=geo.gettoptracks&api_key=c1572082105bd40d247836b5c1819623&format=json&country=netherlands" response, err := http.get(url) if err != nil { fmt.printf("%s\n", err) os.exit(1) } de...
Read more