Anyone good with SQL?

JohnB47

Thanks. Your quoted suggestion is way above my head and way too complex for my simple home expenses needs. Also I have no idea what "use third normal form in your database design" means, which perhaps demonstrates that I would be ill advised to go down that route.

victor2

JohnB47 said:

Thanks. Your quoted suggestion is way above my head and way too complex for my simple home expenses needs. Also I have no idea what "use third normal form in your database design" means, which perhaps demonstrates that I would be ill advised to go down that route.

A lot to be said for having a system that works and if it meets your needs, then all well and good.

There are clearly ways you could enhance it if and when you have time to explore the options.

Just knowing those options are there is often sufficient. It's what keeps those with the skill to analyse and process data in work!

Ergates

JohnB47 said:

Thanks. Your quoted suggestion is way above my head and way too complex for my simple home expenses needs. Also I have no idea what "use third normal form in your database design" means, which perhaps demonstrates that I would be ill advised to go down that route.

Using TNF for a home expenses spreadsheet would be adding unnecessary complexity for little gain.  Space* and performance aren't really going to be things you need to be worrying about.   TBH, it's not nearly as important for enterprise level db design as it used to be - space and processing power and *far* cheaper than they used to be.  

For home use, simplicity of data model would be more important considerations.

*If you're carrying out sufficient transactions that you need to consider data volumes in your expenses spreadsheet - then you have a much bigger problem!!