On 8/11/2014 5:11 AM, Tom Davies wrote:
> extremely fast readers who seem to churn through tons of books very
> quickly. So, 17 books/year sounds quite low to me. I guess it might be a
> lot to a 'normal' person (if there is any such person).
Librarians and book vendors have a slightly lower
Hi Mark,
On Tue, 12 Aug 2014 22:37:18 +0100
Mark Bourne wrote:
[snip]
> > Also, then you can localize your status names if you ever want to
> > make your program support other languages.
>
> Something else I haven't had to worry about, but if I did I'd have
> done the localisation in the appl
Paul wrote:
So I was interested, and did a little more digging. I figured I would
share the info.
On Sun, 10 Aug 2014 22:48:43 +0100
Mark Bourne wrote:
I don't know to be honest, not having a lot of experience in database
design. I've only ever really used MySQL, which does support enums,
bu
Calibre is also a great idea/solution for this project, unless one of the
goals of the project is to learn about databases and how to use a database
to solve a real world problem. I added the second clause, because just
learning about databases an admirable goal, but imo, one also should learn
how
Hi Joel,
Some comments on your diagram, in the order I thought of them, not of
importance:
1) I tend to use integers for primary keys. Smallints only go into the
thousands, and most of the stuff I have worked on has needed to be able
to scale well beyond that. Even things that seem small to start
On August 11, 2014 6:44:07 AM PDT, Mark Phillips wrote:
>The framework automatically creates all the plumbing you need to build a
>project (such as database tables), and allows you, the designer, to focus on
>the higher level problems of your design
My impression is that the OP _wants_ to lear
On August 11, 2014 6:28:20 AM PDT, Oogie McGuire wrote:
>Oh Gosh, what do they call folks like me?
>I average 64+ books a year, 1 a week plus one a month.
A prime customer of an independent bookstore.
>year due to textbooks but still…
Students are deliberately excluded from the statistics.
I may be overestimating the simplicity of Base, but I suspect Base will
be far, far simpler than creating a Django project.
A Django project means actual coding, and a lot of it. Yes I know how
simple Django is, but it still requires a decent amount of coding. As I
understand it, Joel isn't a prog
Joel,
A suggestion from left field, but it will help you in the long run. Take a
look at the django project - https://www.djangoproject.com/. It is a
framework for creating database driven web sites. It is very easy to use
and very powerful. The framework automatically creates all the plumbing you
On Aug 10, 2014, at 11:19 PM, Joel Madero wrote:
>> FWIW, the typical "heavy reader" will take 210 years to read a million
>> pages:
>> * "Heavy Reader" being defined as reading 17 books per year.
>> (http://libraries.pewinternet.org/2012/04/04/part-2-the-general-reading-habits-of-americans/)
>
Hi :)
I am not sure if it has been covered in this thread but unlike spreadsheets
with databases you hardly ever read directly from the main tables.
Normally you have "Queries" that filter and do calculations. They look a
LOT like tables such as spreadsheets but they seldom contain ALL the data
f
Hey Jonathan,
responded in line but the gist is - this is a hobby and I'm not going to
spend hours and hours thinking about corner cases/etc... if a book has
multiple authors, I'll pick one, if it belongs to multiple series, I'll
pick one, if it's a spin off to a main series, I'll just track
I'm not horribly worried about name changes ;)
Best,
Joel
On 08/10/2014 07:21 PM, jonathon wrote:
On 8/10/2014 6:48 PM, Joel Madero wrote:
I decided to do the smart thing and diagram it out
Potential issues with the author field:
Book One: Author A & Author B;
Book Two: Author B & Author
On 8/10/2014 6:48 PM, Joel Madero wrote:
> I decided to do the smart thing and diagram it out
Potential issues with the author field:
Book One: Author A & Author B;
Book Two: Author B & Author A;
Book Three: Author A & Author C. Author C is really Author B, but has
had a name change;
Book On
On 8/10/2014 9:50 AM, Oogie McGuire wrote
> If I were doing your system I'd do the following:
> Book table
> Title
> number of pages
> Foreign key links to an authors table and a series table
> boolean read or not or else a link to a table read status see below
> Authors
>
I decided to do the smart thing and diagram it out - the diagram isn't
perfect (looks wise) but I hope that I can get a +1 before actually
making the databases.
Note: I decided to put rankings with date read table, this way I can
have different rankings for the same book (for each instance tha
Hi Joel,
On Sun, 10 Aug 2014 15:49:25 -0700
Joel Madero wrote:
> Gah - I just realized that I think I have to separate "date read"
> from the book info. Reason being that if I read a book 2-3 times and
> want to track the dates then I have to have another table. With this,
> I'd do a one to man
On Sun, 10 Aug 2014 16:48:31 -0600
Oogie McGuire wrote:
> We agree I think my comments passed yours in the mail.
>
> I hadn't done any relational database work until this current big
> project, thats why the database design book I recommended was so
> critical. It got me out of the spreadsh
One reason to keep all the tables separate is to facilitate adding things to
them later. Also localization for other languages and to keep entries exact so
searches are easier to do. Solves issues with How did I spell that? problems in
queries
To my mind the only thing that belongs in a table a
Gah - I just realized that I think I have to separate "date read" from
the book info. Reason being that if I read a book 2-3 times and want to
track the dates then I have to have another table. With this, I'd do a
one to many relationship between the book information and the read date
tables, y
On Aug 10, 2014, at 4:26 PM, Paul wrote:
> Yeah, being able to change these values later is one of the main
> reasons to use a separate table. Clients almost *always* end up adding
> or removing some of these.
>
> Also, when you have specific functionality tied to some of these
> statuses, it's
On Aug 10, 2014, at 3:48 PM, Mark Bourne
wrote:
> you wouldn't generally add or remove status options (and the application may
> assign special meaning to certain statuses, so it may be critical that a
> specific set of values is defined). Then again, in some applications being
> able to int
So I was interested, and did a little more digging. I figured I would
share the info.
On Sun, 10 Aug 2014 22:48:43 +0100
Mark Bourne wrote:
> I don't know to be honest, not having a lot of experience in database
> design. I've only ever really used MySQL, which does support enums,
> but maybe
Paul wrote:
On Sun, 10 Aug 2014 21:30:18 +0100
Mark Bourne wrote:
It looks like each book should only have one of the "ReadStatus"
flags set, so I'd make that an enum field on the BookInformation
table, with possible values of "Not Read", "Reading" and "Read". You
can set the default value for
Thanks all - I have enough to do "something" - probably won't be perfect
but will work for my needs. As for importing the data - not horribly
concerned about this. Very worse case I'll manually enter which won't be
too horrible in my case (really only about 250 entries to put in). More
concerned ab
On Sun, 10 Aug 2014 21:30:18 +0100
Mark Bourne wrote:
> It looks like each book should only have one of the "ReadStatus"
> flags set, so I'd make that an enum field on the BookInformation
> table, with possible values of "Not Read", "Reading" and "Read". You
> can set the default value for the
Hi Joel,
On Sun, 10 Aug 2014 16:02:04 -0400
jomali wrote:
> Joel,
>
> The NumberOfBooksByAuthor and ReadBooksByAuthor fields are
> unnecessary. They can be derived from a simple query for a report.
Agreed.
> Since there has to be a one-to-one relation between the ReadStatus
> table and the
It looks like each book should only have one of the "ReadStatus" flags
set, so I'd make that an enum field on the BookInformation table, with
possible values of "Not Read", "Reading" and "Read". You can set the
default value for the field to "Not Read" so a new record will be set to
that status
Joel,
The NumberOfBooksByAuthor and ReadBooksByAuthor fields are unnecessary.
They can be derived from a simple query for a report.
Since there has to be a one-to-one relation between the ReadStatus table
and the BookInformation table, you might as well merge them. When you do
merge them, a NotRe
Hi All,
So I went back to planning stage. Link to what I think might work -
hoping to get the planning stage done today so I can start actually
putting together the db - I have 3 days off so now's a good time for me
to get the basic structure together :) Thanks in advance!
https://drive.goog
So - I've started with the previous suggestions and am hesitant to
change now (put in about 5 hours over the past couple days to learn by
doing).
Attached is what I have so far. It's pretty basic but just two tables
(as you can see) and a form which I made to my likings.
Suggestions welcome
Really good suggestions!
On Sun, 10 Aug 2014 10:50:48 -0600
Oogie McGuire wrote:
> Do not duplicate data. If you have a field whose contents are
> duplicated then that really probably needs to be a separate table.
Yes, true. Note that if a field is duplicated, is suggests
consolidating into o
I havne't used Base, but I have taken a very complex spreadsheet and designed
an SQL database from it when it became unwieldy. Key things I'd suggest, more
tables is not bad, in fact the more the better if it clearly separates data
into one table. Do not duplicate data. If you have a field whose
On 08/06/14 23:46, Joel Madero wrote:
> Hi All -
>
> So I have been using spreadsheet for about 10 years to keep track of a
> goal that I set my first year of college (reading a million pages before
> I die). That being said, I keep adding things to it and it's becoming
> more and more complicated
Hi All -
So I have been using spreadsheet for about 10 years to keep track of a
goal that I set my first year of college (reading a million pages before
I die). That being said, I keep adding things to it and it's becoming
more and more complicated. This week I decided I wanted to add yet
ano
35 matches
Mail list logo
