I've fixed the problem. For Postgres, I wasn't checking for the case when
there was 0 rows returned.

Regards,
Elias


On 12 May 2014 05:07, Blake McBride <blake1...@gmail.com> wrote:

> It appears to only happen in PostgreSQL.  Also, when I tried it with a
> non-empty file in PostgreSQL, it worked.  Thanks.
>
>
>       SQL∆LoadLib '/home/blake/Backup/apl-sqlite.git/lib_sql.so'
>       db←'sqlite' SQL∆Connect 'yyyy.db'
>       db
> 0
>       'select * from apl_files;' SQL∆Select[db]''
>
> $ sqlite3 yyyy.db
> SQLite version 3.7.17 2013-05-20 00:56:22
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> .schema
> CREATE TABLE apl_files (file_name character varying (80) not null unique);
> sqlite> select * from apl_files;
> sqlite>
>
>
>
> On Fri, May 9, 2014 at 8:14 PM, Elias Mårtenson <loke...@gmail.com> wrote:
>
>> Interesting. Does it happen for all empty tables?
>>  On 10 May 2014 02:27, "Blake McBride" <blake1...@gmail.com> wrote:
>>
>>> APL:
>>>       db←'postgresql' SQL∆Connect 'host=localhost user=postgres
>>> password=postgres dbname=apl'
>>>       db
>>>       'select * from apl_files;' SQL∆Select[db]''
>>>
>>> PostgreSQL:
>>>
>>> $ psql apl postgres
>>> psql (9.1.13)
>>> Type "help" for help.
>>>
>>> apl=# \dt
>>>            List of relations
>>>  Schema |   Name    | Type  |  Owner
>>> --------+-----------+-------+----------
>>>  public | apl_files | table | postgres
>>> (1 row)
>>>
>>> apl=# select * from apl_files;
>>>  file_name
>>> -----------
>>> (0 rows)
>>>
>>> apl=#
>>>
>>> Thanks!
>>>
>>> Blake
>>>
>>>
>>>
>>> On Fri, May 9, 2014 at 9:06 AM, Elias Mårtenson <loke...@gmail.com>wrote:
>>>
>>>> What is the query you ran, and what was the content of the database
>>>> table?
>>>>
>>>> I won't be able to test this on a real Postgres instance until I get
>>>> back home (on Monday), but this information may at least give me an idea.
>>>>
>>>> Regards,
>>>> Elias
>>>>
>>>>
>>>> On 9 May 2014 21:58, Blake McBride <blake1...@gmail.com> wrote:
>>>>
>>>>> Greetings,
>>>>>
>>>>> I've got my keyed file system running on sqlite.  As soon as I started
>>>>> testing it under PostgreSQL I got some errors.  I am thinking that it is
>>>>> possible that you still needed to change the PostgreSQL stuff to match the
>>>>> other changes you had to make for the new API.  This is the error I get:
>>>>>
>>>>> Thanks!
>>>>>
>>>>>
>>>>>
>>>>> ==============================================================================
>>>>> Assertion failed: 0
>>>>> in Function:      init
>>>>>  in file:          Cell.cc:48
>>>>>
>>>>> Call stack:
>>>>>
>>>>> ----------------------------------------
>>>>> -- Stack trace at Cell.cc:48
>>>>> ----------------------------------------
>>>>> 0x7f3b16e95de5 __libc_start_main
>>>>> 0x4359fd  main
>>>>> 0x52993d   Workspace::immediate_execution(bool)
>>>>> 0x46504d    Command::process_line()
>>>>> 0x463ec3     Command::process_line(UCS_string&)
>>>>> 0x46f4e8      Executable::execute_body() const
>>>>> 0x4e4040       StateIndicator::run()
>>>>> 0x491f9a        Prefix::reduce_statements()
>>>>> 0x48db6e         Prefix::reduce_V_ASS_B_()
>>>>> 0x4f4386          Symbol::assign(Value_P, char const*)
>>>>> 0x52600b           Value::clone(char const*) const
>>>>> 0x45b3e1            Cell::init(Cell const&)
>>>>> 0x44386f             do_Assert(char const*, char const*, char const*,
>>>>> int)
>>>>> ========================================
>>>>>
>>>>> SI stack:
>>>>>
>>>>> Depth:    2
>>>>> Exec:     0x2602448
>>>>> Pmode:    ∇ SQL∆Select[1]
>>>>> PC:       10 ENDL
>>>>> Stat:     Z←X SQL[3,db] Y
>>>>> err_code: 0x0
>>>>> thrown:   at StateIndicator.cc:40
>>>>> e_msg_1:  'No Error'
>>>>> e_msg_2:  ''
>>>>> e_msg_3:  ''
>>>>>
>>>>> Depth:    1
>>>>> Exec:     0x25e6708
>>>>> Pmode:    ∇ KF∆Files[1]
>>>>> PC:       6 ←
>>>>> Stat:     files←'select file_name from apl_files;' SQL∆Select[db]''
>>>>> err_code: 0x0
>>>>> thrown:   at StateIndicator.cc:40
>>>>> e_msg_1:  'No Error'
>>>>> e_msg_2:  ''
>>>>> e_msg_3:  ''
>>>>>
>>>>> Depth:    0
>>>>> Exec:     0x26011a0
>>>>> Pmode:    ◊  db KF∆Files db
>>>>> PC:       3 ENDL
>>>>> Stat:     db KF∆Files db
>>>>> err_code: 0x0
>>>>> thrown:   at StateIndicator.cc:40
>>>>> e_msg_1:  'No Error'
>>>>> e_msg_2:  ''
>>>>> e_msg_3:  ''
>>>>>
>>>>>
>>>>>
>>>>> ==============================================================================
>>>>>
>>>>>
>>>>> ====================================================
>>>>> SEGMENTATION FAULT
>>>>>
>>>>> ----------------------------------------
>>>>> -- Stack trace at main.cc:122
>>>>> ----------------------------------------
>>>>> 0x7f3b16e95de5 __libc_start_main
>>>>> 0x4359fd  main
>>>>> 0x52993d   Workspace::immediate_execution(bool)
>>>>> 0x46504d    Command::process_line()
>>>>> 0x463ec3     Command::process_line(UCS_string&)
>>>>> 0x46f4e8      Executable::execute_body() const
>>>>> 0x4e4040       StateIndicator::run()
>>>>> 0x491f9a        Prefix::reduce_statements()
>>>>>  0x48db6e         Prefix::reduce_V_ASS_B_()
>>>>> 0x4f4386          Symbol::assign(Value_P, char const*)
>>>>> 0x52600b           Value::clone(char const*) const
>>>>> 0x45b3e1            Cell::init(Cell const&)
>>>>> 0x443817             do_Assert(char const*, char const*, char const*,
>>>>> int)
>>>>> 0x50131c              TestFiles::assert_error()
>>>>> 0x7f3b186efbb0
>>>>> 0x47f0aa
>>>>> ========================================
>>>>> ====================================================
>>>>>
>>>>> Process apl segmentation fault
>>>>>
>>>>>
>>>>
>>>
>

Reply via email to