Re: OT : Advice on SQL database design

Very good write up. At least form this one particular test, it seems that SQL is faster than any of the other methods, especially MongoDB. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin

Re: OT : Advice on SQL database design

> I'm particularly interested in the idea of NoSQL databases - they > seem too good to be true :-) You can even get both in one: http://wiki.postgresql.org/images/b/b4/Pg-as-nosql-pgday-fosdem-2013.pdf Sincerely, Wolfgang ___ use-livecode mailing li

Re: OT : Advice on SQL database design

Alex- Thursday, July 3, 2014, 5:06:16 PM, you wrote: > I'm particularly interested in the idea of NoSQL databases - they seem > too good to be true :-) Well, be careful with nosql databases. In many cases they are indeed too good to be true. You need to be very specific with your needs. -- -Ma

Re: OT : Advice on SQL database design

On 01/07/2014 13:17, Robert Brenstein wrote: You will get lots of advice, I am sure. Database design is a science and an art. What helps often is to identify data along the lines of I did indeed get lots of good advice - many thanks to all who replied. So many new things to read about

Re: OT : Advice on SQL database design

On 01.07.2014 at 1:23 Uhr +0100 Alex Tweedly apparently wrote: I guess there's a meta-question about "what's a good book/source on SQL database design ?" I am trying to design a database. There is one table which contains, let's say, Armed Forces Personnel - each row is a different person -

Re: OT : Advice on SQL database design

> lcSQL Software Have you ever thought of implementing something like a "Naked Objects" framework for Livecode? http://en.wikipedia.org/wiki/Naked_objects https://isis.apache.org/intro/learning-more/Pawson-Naked-Objects-thesis.pdf Sincerely, Wolfgang

Re: OT : Advice on SQL database design

> I guess there's a meta-question about "what's a good book/source on > SQL database design ?" http://tinyurl.com/mrab534 http://tinyurl.com/md84k87 Sincerely, Wolfgang ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url

Re: OT : Advice on SQL database design

I'll try to provide some initial info: On 1 Jul 2014, at 10:23 am, Alex Tweedly wrote: > I guess there's a meta-question about "what's a good book/source on SQL > database design ?" > > I am trying to design a database. There is one table which contains, let's > say, Armed Forces Personnel >

Re: OT : Advice on SQL database design

Hi Alex, Your situation seems to involve a 1-1 relationship between tables which always feels a little strange for the reasons you mentioned. I'd probably eliminate option A for starters. Following classic database design rules, you should probably have a separate table for each armed forces bran