A Table with only one record

If you were creating a database and one of the tables was only going to have one record to hold app settings, would you create a table with a column for each setting or a table with 3 columns id, property, value and just store the settings as property value pairs?

the latter - 3 columns id, property, value
that way when you find you need to add more you can without having to revamp the table

[quote=68878:@Norman Palardy]the latter - 3 columns id, property, value
that way when you find you need to add more you can without having to revamp the table[/quote]

Thanks Norman. I was leaning towards this for that reason.