coup de coeur (is not faieur)
category: general [glöplog]
Personally, I think a coup de coeur for each category would be the only sufficient way for the kind of this site. You simply cannot separate three stunning demos from 64k or whatever...
I guess most of us can handle configuring this;) and you only have to connect different db tables. oh maaan that would be great. Most likely this even can be used for stat calcs
I guess most of us can handle configuring this;) and you only have to connect different db tables. oh maaan that would be great. Most likely this even can be used for stat calcs
It's been mentionned a few times that so far the CDC are in the USER table, so your suggestion is technically impossible now.
Just so you know.
Just so you know.
besides that is really missing the point with cdc
With the current implementation, getting more CDC take some time for the users, so they have more value as ( in theory ) they are given more wisely.
I want a new CDC anyway... ARTE is up there for way too long. :/
Man that's bad db design... Because CDC<->USER relation is many-to-many, there should be a third table to unravel that relation, like a table with foreign keys to user-table and prods-table.
And, if different kind of prods are on different tables (one for intros, one for demos etc) that's Really bad design. Let's say that you wanted to add a new info for a prod, f.ex. "who coded this" or whatever, you'd have to add this column to all the tables that represent things that might have a coder involved...
But hey, all bad db design does is bad performance and pain in the ass to code, nothing serious :) And these are based on assumptions made here, not the actual db (hopefully).
And, if different kind of prods are on different tables (one for intros, one for demos etc) that's Really bad design. Let's say that you wanted to add a new info for a prod, f.ex. "who coded this" or whatever, you'd have to add this column to all the tables that represent things that might have a coder involved...
But hey, all bad db design does is bad performance and pain in the ass to code, nothing serious :) And these are based on assumptions made here, not the actual db (hopefully).
rainmaker: I know all that. I'm not a Pouet admin. The making of Pouet seems pretty empircal and incremental. There seems to be many false good ideas in the DB design. If only some skilled person really had time to re-create Pouet from scratch with a somewhat future-proof DB and template design.
well, we have pouet 2.0 now... ;)
Does somebody actually care about these? ;)
I think that the limited availability of coup de coeurs makes a lot of sense, because it 1. forces you to think hard when choosing them and 2. pushes you into changing them every once in a while.
The decisions are painful, but this is exactly the point of any _real_ decision.
The decisions are painful, but this is exactly the point of any _real_ decision.
You smell that? It smells like rotten thread. We have a necroposter here! :)
Neko post: 