Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
2 7 15
Impact
~58k people reached

  • 0 posts edited
  • 0 helpful flags
  • 7 votes cast
Mar
28
awarded  Famous Question
Feb
24
awarded  Notable Question
Sep
13
awarded  Promoter
Sep
13
comment Form builder schema for SQL database?
But that'd result in a huge performance hit. Let's say a form is created, and millions of submissions against it are recorded. Without indices and other db features, answering aggregate and even simple SELECT queries would become really inefficient. I'm not talking about exposing a whole Microsoft Access-esque interface, but a simple form builder (with PK, FK and indexes) shouldn't be nontrivial to create.
Sep
5
asked Form builder schema for SQL database?
Jun
2
asked Loop through fields on a before-insert trigger?
May
27
awarded  Notable Question
Dec
15
awarded  Notable Question
Aug
26
awarded  Notable Question
Jul
2
awarded  Curious
Apr
1
awarded  Popular Question
Jul
16
awarded  Famous Question
Jun
25
awarded  Popular Question
Jun
13
awarded  Notable Question
May
21
awarded  Popular Question
Apr
25
comment Switching to NoSQL for native JSON use?
Thanks for your comments, I have upvoted this.
Apr
21
asked Switching to NoSQL for native JSON use?
Apr
8
accepted Defining constraints in `CREATE TABLE` statements
Mar
18
comment Defining constraints in `CREATE TABLE` statements
Phil/a_horse_with_no_name [BTW: Clint Eastwood parody? =P]: So it seems that there are some advantages with keeping things self contained, and other advantages (see answer by @MikeSherrill'Catcall') for keeping them separate. Maybe I just need to flex my Python knuckles and build a two-way script? :) - Leigh: Guessing that constraints incur less overhead? - Mike:\t\t\t\tIndentation FTW!
Mar
18
comment Defining constraints in `CREATE TABLE` statements
Wow, that's a very useful use-case that I hadn't considered! +1