Hi Simon,
no its OK -- did not take anything personal. I think I stay with my
SQL-statements...
Thanks again for your hint,
Tobias
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-user
On 25 Dec 2013, at 8:54am, Tobias Steinmann wrote:
> thanks for your hint. I needed some time to figure out, how to use this
> mailing-list and I hope, you will get my answer.
>
> I tried the same im MySQL and it worked -- I know, that is no reason I just
> wanted to say.
>
> I also tried, t
Hi Simon,
thanks for your hint. I needed some time to figure out, how to use this
mailing-list and I hope, you will get my answer.
I tried the same im MySQL and it worked -- I know, that is no reason I
just wanted to say.
I also tried, to rename one of the depth's to depth1 -- and then it al
On Mon, 23 Dec 2013 23:50:30 +0100
"E.Pasma" wrote:
> > . See if you can make the simplest possible SELECT that comes up
> > with unexpected results.
>
> select 0 as depth
> from(select 1 as depth)
> group by null
> having depth < 1
> ;
> This returns no rows. Thus the HAVING clause refer
Op 23 dec 2013, om 14:32 heeft Simon Slavin het volgende geschreven:
General note: when making up a name for a calculation like 'depth',
try to make sure it's not the name of any of the columns in the
tables mentioned in your SELECT. This avoids ambiguity.
. See if you can make the simp
On 22 Dec 2013, at 11:12pm, Tobias Steinmann wrote:
> SELECT node.id,node.lft, node.rgt, (COUNT(parent.id) - (sub_tree.depth + 1))
> AS depth FROM target_directory AS node, target_directory AS parent,
> target_directory AS sub_parent, (SELECT node.id, (COUNT(parent.id) - 1) AS
> depth FROM ta
Hi,
I have a strange behaviour of SQLITE with a HAVING-Clause and I don't
find the problem. Possibly a bug in SQLITE?
Following Query regarding a nested tree set to get all children of a node:
SELECT node.id,node.lft, node.rgt, (COUNT(parent.id) - (sub_tree.depth +
1)) AS depth FROM target_di
7 matches
Mail list logo
