Hi,
I will look into it. ./configure should properly detect if sqlite or
postgres is
installed and compile only those pieces that are installed.
BTW if you get 0 from ⎕FX then )MORE shows where it was searching
for the .so files. That doesn't help here but might be of interest.
/// Juergen
I also noticed that the community web page says that the library supports
mysql and postgres, when in fact it supports SQLite and PostgreSQL.
Regards,
Elias
On 6 July 2014 17:29, Juergen Sauermann
wrote:
> Hi,
>
> I will look into it. ./configure should properly detect if sqlite or
> postgres
Hi Elias,
there also seems to be an issue with PQconnectdbParams()
I have it defined in /usr/include/postgresql/libpq-fe.h on one (newer:
linux-mint 16) machine
but not in the same file on an older (Ubuntu 12.04 machine).
/// Jürgen
On 07/06/2014 11:32 AM, Elias Mårtenson wrote:
I also not
Hi,
I have improved the check for postgresql in ./configure, see SVN 360.
Seems like SQLite does such a test already.
Since lib_sql is a shared library it can still happen that it compiles but
complains at runtime when another shared lib that it depends on cannot
be found.
/// Jürgen
On 07/0
Hi David,
I believe there is (in *m4/ax_lib_sqlite3.m4*).
/// Jürgen
On 07/05/2014 08:24 PM, David B. Lamkins wrote:
Nice.
Should there be a ./configure check for the sqlite3.h file?
On Sat, 2014-07-05 at 16:03 +0200, Juergen Sauermann wrote:
Hi,
I have added Elias' SQL code (native funct
Hi David,
thanks, it is a bug. Fixed in SVN 361.
/// Jürgen
On 07/06/2014 05:48 AM, David B. Lamkins wrote:
'5,550.05' ⍕9
9.0
'5,550.05' ⍕99
99.0
'5,550.05' ⍕100
,100.0
'5,550.05' ⍕999
,999.0
'5,550.05' ⍕1000
1,000.0
SQL.apl is located in:
workspaces/SQL.apl
wslib5/SQL.apl
I think it should only be in one place.
Thanks.
Blake
Hi Blake,
yes, sorry. The bug-apl mailing list just passed the 2000'th email and
I did not yet have the time to fully understand the different contributions
related to file systems.
When I briefly read the ISO standard I thought an SQL database with
integers as keys and 10 ⎕CR of
a value would
Dear Juergen,
While the keyed file system is often more desired than a component file
system, the semantics of the two are different enough that one cannot
easily substitute for the other. Having both options would be a good thing
IMO.
David wasn't part of our prior conversation on having the co
When I build and install GNU APL, I specify
--prefix=/home/elias/src/apl/dist. I then expect the PSYS to be
/home/elias/src/apl/dist/lib/apl/wslib*[0-9]*.
Now, typing )LIBS at the prompt gives me: /usr/local/lib/apl/wslib*[0-9]*.
This is not correct, is it?
Regards,
Elias
Hi Blake,
correct. fixed in SVN 362.
/// Jürgen
On 07/06/2014 03:39 PM, Blake McBride wrote:
SQL.apl is located in:
workspaces/SQL.apl
wslib5/SQL.apl
I think it should only be in one place.
Thanks.
Blake
Hi David,
thanks, fixed in SVN 363.
Please note that using a value as right function argument of an operator
is IMHO a rather dubious construct. I know that IBM APL2 allows it, but the
ISO standard is rather unclear about it. On one hand ISO defines the ⍤
operator
using a value *y *as right op
Currently, the function sql∆∆load_library gets called when the SQL.apl gets
executed to load the native library and then gets erased. This is a
problem in the following scenario:
1. Create an APL workspace
2. Copy in the SQL library code (this loads the native library)
3. Save your application
Hi Elias,
)LIBS is currently computed from the location of the running apl binary.
This is sometimes convenient and sometimes not.
A secure way of handling this is to have the paths in the user's
preferences file.
I believe that some of the libs (wslib3, 4, and 5) are installed in the
locati
Actually I don't have any APL binary installed anywhere else.
Regards,
Elias
On 6 Jul 2014 23:16, "Juergen Sauermann"
wrote:
> Hi Elias,
>
> )LIBS is currently computed from the location of the running apl binary.
> This is sometimes convenient and sometimes not.
>
> A secure way of handling th
Hi Elias,
I would still need the apl -l 37 output to see what is happening.
BTW the second column in )LIBS shows where the path comes from.
If it shows PSYS (like you said below) then it comes from the system's
preference file. The question is then: which one? This is what apl -l 37
will tell us
I wasn't previously aware that an appendix of the ISO standard called
for a component file system. Thanks for calling that to my attention.
I based my API on a vague recollection of component file systems of days
past. (In particular, STSC's component files as implemented in Richard
Smith's short-
I have the ISO component file implementation up and running. Give me a few
days to polish and test, then I'll post the code to Github.
On Jul 6, 2014 1:47 PM, "David B. Lamkins" wrote:
> I wasn't previously aware that an appendix of the ISO standard called
> for a component file system. Thanks fo
18 matches
Mail list logo
