So basically when a person.

Point: Its a developer machine server

Varieur: Buddd: answer my question instead?

Varieur: 2015-09-07 21:02:25 Varieur buddd: depend on how it was installed / started

Hanserd: What question are you asking me?

Varieur: Buddd: how did you install MySQL, and how did you start it?

Barscewski: I installed it through whatever you download off mysql webpage, its a developer machine server

Josich: I’m not sure how i started it =

Varieur: You don’t know how it started?

Teitel: I think it started automatically after i installed it

Varieur: Buddd: does your OS have services?

Joanis: I’m not sure what you’re asking here, i’m in windows 7

Varieur: Buddd: no idea, I don’t use windows. I’m asking you.

Seybold: Apparently windows does have services

Wallingford: But i need to stop the server before I can install them

Spraberry: Anyone know how to turn off a mysql server in windows?

Bilkiss: Its on a developer machine, hogging ram

Varieur: Buddd: figure out your services, IMO

Horio: Hi, can some advice me on ways to implement my “relationships” table for a social site?

Moscariello: Right now I’m faced with a decision as to whether save 1 relationship type per user per row, or have all relationships to a given entity combined in a single row

Christe: I guess single row would be much better for lookup, however there are some maintenance problems

Tarboro: Such as supose I user has liked some node and later blocked it.

Sardinha: Now those are 2 possibly conflicting informations that I have to account for for instance, if deciding to show information about the object in the subjects timeline

Luckenbach: Because even thou it was previously liked, it has also been blocked later, so I either have to take both rows in account in my business logic or remove the like row

Varieur: JFlash: person friend person1_id, person2_id

Rathman: Hello Varieur, nice to hear from you

Topete: I must say I dont have friends table, I only plan to have a relationships table. see my list of possible relationships here:

Jacobsma: Btw, the idea is to use a single relationship table for all nodes

Asselta: Regarless of node type

Varieur: You can go that route too.

Pin: Ok but the question is about using a single relationship record for row, vs having allrelationships towards 2 entities grouped in a string array

Carrigg: I have performance concerns with the latter approach, and maintenance concern with the former

Varieur: JFlash: never store comma-separated values in the same column.

Varieur: JFlash: one value per row.

Entsminger: Ok but if go this way, that will make my code looks like hell because in most of my queries I will have to also take into account if the user has banned, blocked, been removed and so on and so forth. see the problem?

Hamm: Cool so it’ll be even worse if you try to store arrays of data in one column

Germinaro: Unless I make it so that negative relationships update/erase good relationships

Haroldsen: JFlash:

Manross: Musicians join bands, play for a period, quit, rejoin.

Varieur: JFlash: that’s the danger with comma-separate values.

Kirt: Btw, I just had an idea. I could use a secondary collum to invalidate aka, “flag” those relationships affected!

Varieur: Sure. But avoid the list of doom.

Auala: For instance, I could have a column called relationship_active which can be false/true

Kaewprasert: So basically when a person blocks another I set false in the active column of the like relationship