Database Design #2

Open
MisterPhilip opened this Issue Sep 6, 2012 · 12 comments

Comments

Projects
None yet
6 participants
Contributor

MisterPhilip commented Sep 6, 2012

Need to finalize the database design for all specifications. I do believe Ignace has started on some of this on the development forums for one of the specs. However, we'll need to do this for all of the specifications.

@ghost ghost assigned ignace Sep 7, 2012

Contributor

MisterPhilip commented Sep 26, 2012

@ignace - do you think it makes sense to continue on this while @trq works on the view stuff for proem?

Member

trq commented Sep 26, 2012

@MisterPhilip, we need to catch up in irc. I'm really starting to think we might need to go down a different path.

I seriously have no time on my hands at the moment after going back to work.

philip commented Sep 26, 2012

Wrong @philip, I think you mean @MisterPhilip ... I received an email and wondered "What did I agree to do this time?" :)

Owner

gizmola commented Sep 26, 2012

We can always go back to Symfony2.

On Tue, Sep 25, 2012 at 7:47 PM, Tony R Quilkey notifications@github.comwrote:

@philip https://github.com/philip, we need to catch up in irc. I'm
really starting to think we might need to go down a different path.

I seriously have no time on my hands at the moment after going back to
work.


Reply to this email directly or view it on GitHubhttps://github.com/PHPFreaks/site/issues/2#issuecomment-8877318.

Contributor

MisterPhilip commented Sep 26, 2012

Ha, sorry @philip - too many of us Philip's in the world ;)

@trq - yeah, if we need to switch back to sf2, that's fine. I know @gizmola would be happy.

Contributor

MisterPhilip commented Sep 26, 2012

Okay, just talked with @trq. We'll use sf2 for the project now, since he might not have enough time to work on proem for our uses.

Owner

gizmola commented Sep 26, 2012

Ha, sorry @philip https://github.com/philip - too many of us Philip's
in the world ;)

@trq https://github.com/trq - yeah, if we need to switch back to sf2,
that's fine. I know @gizmola https://github.com/gizmola would be happy.

Well, I was resolved to go with Proem, but the pressure that puts Tony
under is pretty significant. I felt like we were going to have to twiddle
our thumbs until he could get some things worked out, and with a new baby
that's a lot to expect of anyone. Since we were going to use some of the
same components that are in symfony, this is probably the next best thing.

Member

trq commented Sep 26, 2012

Yeah sorry guys. It's probably a bit much to chew in one go.

I'll be around, and will be still working on Proem, but yeah, all the best
with stuff.

On Wed, Sep 26, 2012 at 2:46 PM, David Rolston notifications@github.comwrote:

On Tue, Sep 25, 2012 at 9:37 PM, Philip Lawrence
notifications@github.comwrote:

Ha, sorry @philip https://github.com/philip - too many of us Philip's
in the world ;)

@trq https://github.com/trq - yeah, if we need to switch back to sf2,
that's fine. I know @gizmola https://github.com/gizmola would be
happy.

Well, I was resolved to go with Proem, but the pressure that puts Tony
under is pretty significant. I felt like we were going to have to twiddle
our thumbs until he could get some things worked out, and with a new baby
that's a lot to expect of anyone. Since we were going to use some of the
same components that are in symfony, this is probably the next best thing.


Reply to this email directly or view it on GitHubhttps://github.com/PHPFreaks/site/issues/2#issuecomment-8878864.

Contributor

premiso commented Oct 11, 2012

Ok, so it seems we need to figure out a naming strategy.

http://docs.doctrine-project.org/en/latest/reference/namingstrategy.html

I put in a vote for the _'s where necessary and all lowercase names.

As far as the primary ID, I prefer it to just be id, but we just need to figure out having it as table_id or just id. Voice your opinion, and once we have the basic naming strategy laid out, we can more effectively work on creating the structures.

Contributor

MisterPhilip commented Oct 11, 2012

I'm used to running it as table_id, but I'm fine with not here. As long as any FK's have the table name in front of them, I'm fine with it. (see example below)

user
-------------
id
name
article
-------------
id
name
user_id (references user.id)
Contributor

premiso commented Oct 11, 2012

I would like to adhere to some standard but I am finding it hard to locate a decent SQL writing standard that people use.

So yea, let's go with id for the primary key and then any foreign keys need the table_id. Unless there is a valid argument and or an actual document we can go by and adhere to, that is what we will stick to.

Contributor

MisterPhilip commented Oct 28, 2012

Bump to see if anyone has had time to make any progress on this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment