Re: Call for current news site data formats

[Patrick Lenz <scoop@freshmeat.net>]

On Sun, 9 Aug 1998, Christopher Blizzard wrote:

> Here's mine...not much to it.  :)

Mine's not exciting either, I just have two separate tables, one for the
application index and one for the news articles. The contribution system
for application announcements uses the appindex table to gather already
known data. Field definitions to follow:

mysql> describe news;  
+-------------+-------------+------+-----+---------+-------+
| Field       | Type        | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| when        | int(12)     |      | MUL | 0       |       |
| who         | varchar(50) | YES  |     | NULL    |       |
| topic       | varchar(80) | YES  |     | NULL    |       |
| body        | text        | YES  |     | NULL    |       |
| contributed | char(3)     |      | MUL | 0       |       |
| email       | varchar(50) | YES  |     | NULL    |       |
| category    | varchar(15) | YES  |     | NULL    |       |
+-------------+-------------+------+-----+---------+-------+


mysql> describe appindex;
+---------------+--------------+------+-----+---------+-------+
| Field         | Type         | Null | Key | Default | Extra |
+---------------+--------------+------+-----+---------+-------+
| when          | int(12)      |      | MUL | 0       |       |
| who           | varchar(50)  | YES  |     | NULL    |       |
| email         | varchar(50)  | YES  |     | NULL    |       |
| topic         | varchar(80)  | YES  |     | NULL    |       |
| site          | varchar(80)  | YES  |     | NULL    |       |
| version       | varchar(80)  | YES  |     | NULL    |       |
| author        | varchar(80)  | YES  |     | NULL    |       |
| authoremail   | varchar(80)  | YES  |     | NULL    |       |
| category      | varchar(80)  |      | MUL | 0       |       |
| description   | text         | YES  |     | NULL    |       |
| rpm           | varchar(80)  | YES  |     | NULL    |       |
| coauthor      | varchar(80)  | YES  |     | NULL    |       |
| coauthoremail | varchar(80)  | YES  |     | NULL    |       |
| betaversion   | varchar(80)  | YES  |     | NULL    |       |
| license       | varchar(80)  | YES  |     | NULL    |       |
| deb           | varchar(80)  | YES  |     | NULL    |       |
| section       | varchar(80)  |      | MUL | 0       |       |
| download      | varchar(120) | YES  |     | NULL    |       |
| oneliner      | varchar(80)  | YES  |     | NULL    |       |
+---------------+--------------+------+-----+---------+-------+



> Well, every site has different data requirements.  I'm going to guess
> that most of them are using mysql as a database backend, apache with
> perl as a module.  Personally, my pages are generated using perl from a
> mysql backend but are generated static html pages, no includes or
> anything.

It's apache with PHP3 on my end, generated on the fly due to the fact I
need high flexibility regarding the data available.

-- 
   __/\__ 
   \ oO / .. scoop@freshmeat.net
    |/\|  .. freshmeat crew