Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 6
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Sep
14
comment PostgreSQL not using index
It works very well - even setting it to 2 tips it.
Sep
14
accepted PostgreSQL not using index
Sep
14
comment PostgreSQL not using index
I will try this out shortly. In the meantime, I cannot seem to find an overview of the various cost parameters default settings - do you know if there is one?
Sep
14
comment PostgreSQL not using index
Some rows are a few thousand chars long, others are long enough that they need to be split up into multiple row. I would only need the id as it identifies the document. I realize that the above table have the id as being the primary key. That is not how the final table will look.
Sep
11
asked PostgreSQL not using index
Apr
28
awarded  Notable Question
Feb
17
awarded  Popular Question
Aug
1
awarded  Supporter
Aug
1
comment Why does altering a table and adding a foreign key create an extra constaint?
I figured that out, but thanks for the explanation.
Jul
31
awarded  Editor
Jul
31
revised Why does altering a table and adding a foreign key create an extra constaint?
added 399 characters in body
Jul
31
comment Why does altering a table and adding a foreign key create an extra constaint?
The name gives it all away, but I've not worked with sql-server much, so it's all learning. For the curious I edited the question with the solution.
Jul
31
awarded  Scholar
Jul
31
accepted Why does altering a table and adding a foreign key create an extra constaint?
Jul
31
comment Why does altering a table and adding a foreign key create an extra constaint?
I feel slightly stupid now. I added the extra column with a NOT NULL and DEFAULT statement, which of cause results in a constraint. Thanks for pointing me in the right direction.
Jul
30
awarded  Student
Jul
30
asked Why does altering a table and adding a foreign key create an extra constaint?
Jul
30
awarded  Teacher