naviserver-devel

[naviserver-devel] Buglets

[Ian H. <har...@gm...>]

Here are a couple things I've found during my migration from AOLServer
to Naviserver.

1.  The order of arguments to ns_register_filter is reversed.  I found
a discussion in the archives talking about this, but no conclusion.
It looks like the procedure args and the filter reason got switched,
which is fine.  I just didn't know.

2.  dbipg does something strange when used with a template, and a
column the same name as the table.  This works as expected:

default:nscp 1> dbi_rows {SELECT classification FROM classification}
UNCLASSIFIED

This does not:

default:nscp 2> dbi_rows {select classificationid, classification from
classification} {
default:nscp 2>>> $classificationid -> $classification
default:nscp 2>>> }

1 -> 1

3.  ns_cp is broken.  I read in the archives that this command was to
be deprecated.  So I quit using it.  What it did was fail with a
permission error which is funny because [exec cp ...] did not fail.
Maybe those commands should just be removed.  There is going to be
some pain migrating anyway...

So far so good.  Thanks for all your work on this project!

- Ian

Re: [naviserver-devel] Buglets

[Stephen D. <sd...@gm...>]

On Mon, Feb 23, 2009 at 10:12 PM, Ian Harding <har...@gm...> wrote:
> Here are a couple things I've found during my migration from AOLServer
> to Naviserver.
>
> 1.  The order of arguments to ns_register_filter is reversed.  I found
> a discussion in the archives talking about this, but no conclusion.
> It looks like the procedure args and the filter reason got switched,
> which is fine.  I just didn't know.


It's like I'm psychic:

  http://wiki.tcl.tk/22567

:-)


> 2.  dbipg does something strange when used with a template, and a
> column the same name as the table.  This works as expected:
>
> default:nscp 1> dbi_rows {SELECT classification FROM classification}
> UNCLASSIFIED
>
> This does not:
>
> default:nscp 2> dbi_rows {select classificationid, classification from
> classification} {
> default:nscp 2>>> $classificationid -> $classification
> default:nscp 2>>> }
>
> 1 -> 1


This works for me, if I'm reading your example right. I've added a
test; can you try it out on your machine?

    http://bitbucket.org/naviserver/nsdbipg/changeset/0fae5f9a2fb9/


> 3.  ns_cp is broken.  I read in the archives that this command was to
> be deprecated.  So I quit using it.  What it did was fail with a
> permission error which is funny because [exec cp ...] did not fail.
> Maybe those commands should just be removed.


Can you add a test which fails to tests/compat.test?

    http://bitbucket.org/naviserver/naviserver/changeset/43cbf8f4f8ae/


Here are some tips for testing naviserver:

    http://wiki.tcl.tk/21659



> There is going to be some pain migrating anyway...


Hope not.  If you run into anything, remember to add it to the wiki.

Re: [naviserver-devel] Buglets

[Ian H. <har...@gm...>]

On Mon, Feb 23, 2009 at 6:29 PM, Stephen Deasey <sd...@gm...> wrote:
> On Mon, Feb 23, 2009 at 10:12 PM, Ian Harding <har...@gm...> wrote:
>> Here are a couple things I've found during my migration from AOLServer
>> to Naviserver.
<snip>

>> 2.  dbipg does something strange when used with a template, and a
>> column the same name as the table.  This works as expected:
>>
>> default:nscp 1> dbi_rows {SELECT classification FROM classification}
>> UNCLASSIFIED
>>
>> This does not:
>>
>> default:nscp 2> dbi_rows {select classificationid, classification from
>> classification} {
>> default:nscp 2>>> $classificationid -> $classification
>> default:nscp 2>>> }
>>
>> 1 -> 1
>
>
> This works for me, if I'm reading your example right. I've added a
> test; can you try it out on your machine?
>
>    http://bitbucket.org/naviserver/nsdbipg/changeset/0fae5f9a2fb9/
>

OK, Nothing to see here.  My PostgreSQL  install was slightly broken.
/usr/lib/libpq.so was pointing to an older version.  All tests pass.
Funny that was the only bug that created...

Thanks!

- Ian