IA/PG/PGM should be a shared data-bank!

[JayTownsend]

I know we took a poll on this already but:

I changed my mind; I think IA/PG/PGM: (Infantry Attacks, Panzer Grenadier, Panzer Grenadier Modern) should all share the same data bank. I mean, the counters, maps and scenario format are the same, only the rules are a bit different but nothing that would be noticed on AAR recording or data/ information lookups.

[waynebaumber]

I know we took a poll on this already but:

I changed my mind; I think IA/PG/PGM: (Infantry Attacks, Panzer Grenadier, Panzer Grenadier Modern) should all share the same data bank. I mean, the counters, maps and scenario format are the same, only the rules are a bit different but nothing that would be noticed on AAR recording or data/ information lookups.

Sorry old boy totally disagree, they are different games, different wars and I see no justification for them sharing databases. No issue with them on the site but should be kept separate.

[JayTownsend]

But why? Data look up is the same and out of convenience, it would be nice to have them all in the same place. But hey, just my opinion.

[Blackcloud6]

Jay, I'm with you that they should be in one database. IA/PG/PG:M may be technically separate game systems but they share a common base. And their difference show the evolution of warfare at this scale in the 20th Century. To me, bringing them together strengthens the history aspect of the game. It is also more convenient to have one database to serve the whole and thus more people will use the IA and PG:M portions. Build it and they will come.

Sorry for being a bit late to this party as other gaming adventure kept me away from PG lately. I was one who asked for this. I'm surprised there is not more discussion. Don't let that sway you, I do think people will, at the end of the day, appreciate the coming together of all three in this wonderful database and site you have created.

[Matt W]

I have to think that, in the end, it is more important for IA and PG:M to have a place to "be" than it is to have separate databases. I am happy either which way it works. I just want it to be in place!

[vince hughes]

Perhaps it would be easier to have them all added to the one database anyway ?

That way everything is viewable from the same 'clicks'.

[tlangston28]

Perhaps it would be easier to have them all added to the one database anyway ?

That way everything is viewable from the same 'clicks'.

Technically speaking, the location of the data would not affect the "viewable from the same clicks" feature, as Shad would probably attest. The data could be held in a separate database and still be viewable on the same site, it is just that it would be work to get it going (whichever way it goes).

If it was put in the same database, additional fields and tables would probably need to be added to at least identify which "era" game-system the game would represent, as well as the different fields that would have to cover those data pieces that do not exist in PG WWII. In a separate database, it could be built to suit the requirements of the game system and still be combined with the existing database through queries combining the common data built into the website pages (which would probably need to be new pages). I don't know how MySQL would handle these types of queries but I know it could work.

[thomaso827]

I'm honestly not sure about the IA and PGM games but would like to see the Korean War stuff added in, anyway. It's not modern, uses the standard (or new standard) 4th edition rules, and falls only a short time after several of the other post-WW2/Cold War/alternative war games already on the list.

[larry marak]

Jay's Korean magnum opus (great work, not Opie's ice cream bar) is part of the PG series and will be entered into the db eventually, as the monks entering the data continue to scribble away.

[richvalle]

Sorry... off topic... Is that process open to anyone that has a new game? I don't have these games but I hope (hope!) to get An Army at Dawn soon and I was thinking I could help enter in data here.