Jim,
My data used to be hard coded into my app but now I am porting to
Android and the rules have changed. I need smaller subs so the database
fills the need to make my large subs smaller due to hard coded data. So
in reality I just need a flat file or as you as say, a denormalized
database. I figured I would learn the normalized way as years ago I was
trying to figure that out with Access (with no success). But I am also
learning Android programming (very early stage), and see that it will be
easier for me to have a denormalized db for now. My db will be "read
only" too. So that makes its use more like hard coded data which I want
and need. When I learned VB years ago I got stumped often but over time
things started to "click". I am waiting to hear those clicks with SQLite
soon. :)
Thanks,
Dave
(also in Florida)
On 3/7/2015 8:03 PM, Jim Callahan wrote:
> The appropriate structure of the database depends on whether you need the
> tables spread out into multiple tables for consistency ("one fact in one
> location") -- a process called "normalization or whether you want all the
> data in one table for ease of querying ("denormalization").
>
> Transactional systems are usually designed to be normalized; while decision
> support tables may be more de-normalized (for ease of querying).
>
> If you want to combine your tables along the primary key, the way to do it
> in SQL is to create SELECT ...JOIN queries and then when you have a working
> join query that has the struture you want you have a choice of using the
> SELECT...JOIN query as if it was table or converting the query to a table
> with a CREATE TABLE FROM SELECT ...JOIN query.
>
> Jim Callahan
> Orlando, FL
>
> On Sat, Mar 7, 2015 at 8:18 PM, Darren Duncan <darren at darrenduncan.net>
> wrote:
>
