Click here to Skip to main content
15,911,141 members
Home / Discussions / Database
   

Database

 
GeneralRe: Please assist to solve this problem Pin
pubududilena3-Oct-06 19:47
pubududilena3-Oct-06 19:47 
GeneralRe: Please assist to solve this problem Pin
Michael Potter4-Oct-06 4:00
Michael Potter4-Oct-06 4:00 
QuestionOrdering a linked list Pin
Rob Philpott1-Oct-06 23:34
Rob Philpott1-Oct-06 23:34 
AnswerRe: Ordering a linked list Pin
Colin Angus Mackay2-Oct-06 0:41
Colin Angus Mackay2-Oct-06 0:41 
GeneralRe: Ordering a linked list Pin
Rob Philpott2-Oct-06 1:11
Rob Philpott2-Oct-06 1:11 
GeneralRe: Ordering a linked list Pin
Colin Angus Mackay2-Oct-06 2:01
Colin Angus Mackay2-Oct-06 2:01 
GeneralRe: Ordering a linked list Pin
Rob Philpott2-Oct-06 3:01
Rob Philpott2-Oct-06 3:01 
GeneralRe: Ordering a linked list Pin
Colin Angus Mackay2-Oct-06 8:04
Colin Angus Mackay2-Oct-06 8:04 
From what you describe I don't think you need intermediate tables. A compound primary key on the note table might suffice, assuming you don't have one note that needs to be shared among multiple other tables.

The MainId would be what other tables use to link to the notes - so it uniquely defines a group of notes. The SecondaryId is just to uniquely identify each note within the group.

Perhaps that might work. If your system is going to be busy and there may be the scenario where two processes want to create a new group of notes simultaneously then I'd recommend a GUID for the MainId because they won't collide as you cannot use an Identity because it would cause problems when you wanted to put a second note in an existing group and you can't use MAX(MainId) because two processes might try the same thing at the same time.

Your other option is intermediate tables. I don't really think they clutter up the place, but if your think they do, then you could always prefix their name with something to keep them out of the way.


GeneralRe: Ordering a linked list Pin
Colin Angus Mackay2-Oct-06 8:07
Colin Angus Mackay2-Oct-06 8:07 
QuestionLargest Data Typein SQL Server Pin
King Shez1-Oct-06 21:08
King Shez1-Oct-06 21:08 
AnswerRe: Largest Data Typein SQL Server Pin
albCode1-Oct-06 21:25
albCode1-Oct-06 21:25 
AnswerRe: Largest Data Typein SQL Server Pin
Mark Salsbery4-Oct-06 11:02
Mark Salsbery4-Oct-06 11:02 
Questionsql server 2005 Pin
amaneet29-Sep-06 20:21
amaneet29-Sep-06 20:21 
AnswerRe: sql server 2005 Pin
zhengdong jin30-Sep-06 7:32
zhengdong jin30-Sep-06 7:32 
QuestionReplication cursor [modified] Pin
Skanless29-Sep-06 16:18
Skanless29-Sep-06 16:18 
AnswerRe: Replication cursor Pin
Skanless29-Sep-06 21:46
Skanless29-Sep-06 21:46 
QuestionT-SQL Syntax Pin
lakshmi_sri29-Sep-06 11:02
lakshmi_sri29-Sep-06 11:02 
AnswerRe: T-SQL Syntax Pin
zhengdong jin29-Sep-06 19:53
zhengdong jin29-Sep-06 19:53 
Questionshow records horizontally Pin
jlizardo29-Sep-06 5:32
jlizardo29-Sep-06 5:32 
AnswerRe: show records horizontally Pin
Elina Blank29-Sep-06 8:12
sitebuilderElina Blank29-Sep-06 8:12 
QuestionRe: show records horizontally Pin
jlizardo29-Sep-06 9:40
jlizardo29-Sep-06 9:40 
AnswerNot too hard Pin
Ennis Ray Lynch, Jr.2-Oct-06 15:51
Ennis Ray Lynch, Jr.2-Oct-06 15:51 
QuestionPlease help me Pin
honeyman_can29-Sep-06 3:50
honeyman_can29-Sep-06 3:50 
AnswerRe: Please help me Pin
JUNEYT29-Sep-06 4:12
JUNEYT29-Sep-06 4:12 
GeneralRe: Please help me Pin
honeyman_can29-Sep-06 4:24
honeyman_can29-Sep-06 4:24 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.