Andy Goth wrote:
>And honestly, please don't give people with no knowledge of
>SQL theory the power to set your SQL schema in stone.
I am sure you mean Relational Theory, when using a database implementing
Relational semantics, such as SQLite.
There is no requirement that SQL (Structured Query
On 21 May 2014, at 9:16pm, Drago, William @ MWG - NARDAEAST
wrote:
> Well, it finally happened. I had a program crash and was left with a hot
> journal file. A while back there was a post by Richard Hipp detailing
> something that could/should be done before trying to use the database to
> a
All,
Well, it finally happened. I had a program crash and was left with a hot
journal file. A while back there was a post by Richard Hipp detailing something
that could/should be done before trying to use the database to assure that
SQLite does the rollback. I can't find that post now.
Any sug
I fully agree a bad database design can impact you for the life of the
application. If this is a class assignment and the instructor gave you this
as a problem then I can understand "I cannot change it" otherwise fix it
now or pay forever.
*Jim Dodgen*
On Wed, May 21, 2014 at 11:27 AM, Sim
On May 21, 2014, at 6:00 PM, Humblebee wrote:
> At least this is what I'm thinking from my very very limited understanding of
> SQL and with the way that I'm trying to do this.
SMITH: Doctor, it hurts when I do _this_.
DALE: Don’t _do_ that.
with
DataSet
as
(
select 'a,b,c,' as string
),
C
On Wed, May 21, 2014 at 8:45 PM, Jim Dodgen wrote:
> I fully agree a bad database design can impact you for the life of the
> application. If this is a class assignment and the instructor gave you this
> as a problem then I can understand "I cannot change it" otherwise fix it
> now or pay forever
On 21 May 2014, at 7:20pm, Petite Abeille wrote:
> On May 21, 2014, at 6:00 PM, Humblebee wrote:
>
>> only problem is that in this situation, the tables have already been defined
>> and made by someone
>> else so I cannot change it. I'm a bit stuck with the way it is.
>
> Nah… it’s software
On May 21, 2014, at 6:00 PM, Humblebee wrote:
> only problem is that in this situation, the tables have already been defined
> and made by someone
> else so I cannot change it. I'm a bit stuck with the way it is.
Nah… it’s software… you can always change it… in fact, better fix it now… as
th
Andy Goth wrote:
"And honestly, please don't give people with no knowledge of SQL theory the power to
set your SQL schema in stone."
Quote of the day - Probably the single most valuable bit of advice ever!
// I don't do facebook, but if I did, that would go on my wall :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/21/2014 11:09 AM, Stephan Beal wrote:
> On Wed, May 21, 2014 at 6:00 PM, Humblebee
> wrote:
>> | 1 | 4 | 1,5,2,3,4 | | 2 | 5 |
>> 2,6,3,5,1 |
>
> Without doing what Simon suggests, there is no good solution to
>
On 2014/05/21 18:00, Humblebee wrote:
Thank you for your replies.
I'm sorry for not being super clear about the problem:
Note: The parId belongs to another table not shown here.
TeamTable
+-+
| id | parId | personIds |
+-
On Wed, May 21, 2014 at 6:00 PM, Humblebee wrote:
> | 1 | 4 | 1,5,2,3,4 |
> | 2 | 5 | 2,6,3,5,1 |
> +--|
> ...
> @Simon, thank you for showing me a better way to setup the tables,
>
Without doing what Simon suggests, there is no g
Sorry, clicked the send button too quickly.
PersonTable
+--+
| id | name |
+--+
| 4 | john |
| 5 | taylor |
+-+---+
On 5/21/14, fantasia dosa wrote:
> Thank you for your replies.
>
> I'm sorry for not being super clear about
Thank you for your replies.
I'm sorry for not being super clear about the problem:
Note: The parId belongs to another table not shown here.
TeamTable
+-+
| id | parId | personIds |
+-+
| 1 | 4 | 1,5,2,3,4 |
You show a field parId in your TeamTable, but select it from the PersonTable.
Maybe you mean
SELECT * FROM PersonTable WHERE id IN (SELECT personIDs FROM TeamTable WHERE
parId = 4);
-Ursprüngliche Nachricht-
Von: fantasia dosa [mailto:fantasia.d...@gmail.com]
Gesendet: Mittwoch, 21. Mai
On 21 May 2014, at 1:59pm, fantasia dosa wrote:
> TeamTable -
>parId: 4
>personIDs : 1,5,9,6
>
> PersonTable -
> id:
> name:
>
> SELECT * FROM PersonTable WHERE id IN (SELECT personIDs FROM
> PersonTable WHERE parId = 4);
Your problem is cause by the way you're keeping your data.
Hi all wonderful people on this list.
I'm a newbilie so my questions might seem very well-- kinda dumb so
please forgive me.
I'm trying to do the following in Sqlite.
TeamTable -
parId: 4
personIDs : 1,5,9,6
PersonTable -
id:
name:
SELECT * FROM PersonTable WHERE id IN (SELECT p
On 21 May 2014, at 9:36am, Tim Streater wrote:
> On 21 May 2014 at 00:17, RSmith wrote:
>
>> On 2014/05/20 23:37, Tim Streater wrote:
>>> Sorry, should have said I'm on OS X Mavericks 10.9.3.
>>
>> We know... no other OS would report CPU usage as 400%... :)
>
> :-)
>
> Well, to be fair, I
On 2014-05-21 08:36, Tim Streater wrote:
Of course, it might be lying in its teeth for all I know, but the fan
did wind up.
Nah, it wasn't lying. Qt is a huge amount of code,
and Homebrew uses all available processor cores to
compile it. And it still take ages. ;)
+ Justin
_
On 21 May 2014 at 00:17, RSmith wrote:
> On 2014/05/20 23:37, Tim Streater wrote:
>> Sorry, should have said I'm on OS X Mavericks 10.9.3.
>
> We know... no other OS would report CPU usage as 400%... :)
:-)
Well, to be fair, I don't know what OS X was reporting. I have iStat Menus
installed,
As compiling under windows is really a pain I try to avoid it as much as
possible :)
But it should be doable with qmake or cmake with a little tweaking.
But needed libs are Qt and sqlite.
Before I switched to cross-compiling I had an msys environment, but with
some effort it should also work with
21 matches
Mail list logo