ospap - Alpha1

[iago]

Question: What about for the tables and the album page?  In a template, how would you indicate a list? 

Again, I could figure this out myself, but there is probably a "right"er way of doing it :)

<edit> Also, do you think each user should be able to choose a different template for his pages?  Or an individual template for each category, maybe?

<edit2> To answer my first question, I've decided to go with a .php template system, like SMF does.  Hopefully that'll work out ok, it seems like the better way for what I need to do :)

<edit3> Warning: once I get this template stuff set up, I'm probably going to wipe the database again, so don't bother uploading anything complicated :)

[Newby]

I liked OPM (opium) more, but eh, ospap for the win! ;p

[Sidoh]

Why do you wipe the DB anyway, iago?  =p

[iago]

Because I want to make sure my create_tables.sql file works, and because dropping the tables is easier than modifying them :)

[rabbit]

ALPHA 1 IS NO LONGER!!!!

[Sidoh]

Because I want to make sure my create_tables.sql file works, and because dropping the tables is easier than modifying them :)

Is create_talbes.sql a sort of installation file?

[iago]

Because I want to make sure my create_tables.sql file works, and because dropping the tables is easier than modifying them :)

Is create_talbes.sql a sort of installation file?

Yes. 

mysql -u root -p -D ospap < create_tables.sql

[Sidoh]

Yes. 

mysql -u root -p -D ospap < create_tables.sql

Just put them in a different database! :)

[Mythix]

I suggest on your next major release, you dub the version "Opium". I'll even make you a catchy slogan for it!

[iago]

Yes. 

mysql -u root -p -D ospap < create_tables.sql

Just put them in a different database! :)

What difference would that make? Once I change how the database is being used, the original database is completely useless.  It doesn't contain the proper columns!

[Joe]

You should make a column for the database version, and have a routine in the code to upgrade the database.

[iago]

Two problems there
1. I don't plan on changing the database, which isn't a big deal; but
2. I don't want to give my mysql user that much power over the database.  He has select/insert/update/delete, and that's all I'm comfortable with.  I don't even want create/drop. 

[Sidoh]

Or make new code in a different area, and assign it to another database containing the other tables.  It's your project though, so there's no use in me arguing lol.

[iago]

Or make new code in a different area, and assign it to another database containing the other tables.  It's your project though, so there's no use in me arguing lol.

Well, arguing is good, because it helps me learn! I've never used PHP before this, and I've never used MySQL from a user perspective either. 

I don't really understand what you're saying.  What do you mean by "different area"? 

[Sidoh]

Make a copy of the files, then have it get its information from a different database (a near copy of the one that your users are using).  Then you can apply the changes when you're sure it works.  :)

Also -- if you run your queries correctly, you can add and drop columns with little problems.