Hi,
Sometimes I get !MALException:setScenario:Scenario not initialized 'sql'
from the server when I try to start it in scenarios that usually work
without any problems. I can't reproduce it consistently, but sometimes I get
it. What does this exception mean?
Thanks.
--
View this message in context: http://www.nabble.com/Meaning-of%3A-Scenario-not-initialized-%27sql%27-tp26…
Sent from the monetdb-users mailing list archive at Nabble.com.
Since the FEB2010+SP1 release we're encountering loading issues.
With the FEB2010 release we were able to load records until the HDD was full
(500+ million records) on PCs with 2,3 or 24 GB ram memory without going to
the SWAP. This was done by loading CSV-files with 1 million records each
through the COPY INTO command (in the mclient and through a c-script).
Since the FEB2010+SP1 release the system starts to SWAP after loading the
first couple of million records. This results in increased loadtimes per
loaded CSV-file:
1th million: 14 sec
2nd million: 26 sec
3rd million: 44 sec
4th million: 50 sec
5th million: 69 sec
etc.
We have tested this on several PCs and all PCs encounter the same problem.
Test files used are the same for both releases as is the OS (Ubuntu 9.10).
The only variable that has changed is MonetDB.
--
View this message in context: http://old.nabble.com/Loading-problems-since-FEB2010%2BSP1-release-tp282876…
Sent from the monetdb-users mailing list archive at Nabble.com.
Hi,
This still does not work in the latest version - Feb2010+SP2 - on
Windows XP 32bit, Windows Server 2003 64bit,Ubuntu 9.10 64 bit,Fedora 12
64bit. Dariusz.
Martin Kersten wrote:
> Thanks for the example, we will look into it.
>
> dariuszs wrote:
>> Martin,
>> 1) Table schema
>> sql>\d zip_codes
>> CREATE TABLE "sys"."zip_codes" (
>> "zip_code" varchar(5)
>> );
>> sql>
>>
>> 2) From mclient
>> sql>\< /tmp/test.sql
>> MAPI = monetdb@localhost:50000
>> ACTION= read_line
>> QUERY = select count(*) from zip_codes WHERE zip_code IN
>> ('00501','00544','01001','01002','01003','01004','01005','01007','01008','01009','01010','01011','01012','01013','01014','01020','01021','01022','01026','01027','01028','01029','01030','01031','01032','01033','01034','01035','01036','01037','01038','01039','01040','01041','01050','01053','01054','01056','01057','01059','01060','01061','01062','01063','01066','01068','01069','01070','01071','01072','01073','01074','01075','01077','01079','01080','01081','01082
>>
>> ERROR = Connection terminated
>> sql>
>> 3) From shell
>> root@monetdb:/tmp# mclient -lsql < test.sql
>> MAPI = monetdb@localhost:50000
>> ACTION= read_line
>> QUERY = select count(*) from zip_codes WHERE zip_code IN
>> ('00501','00544','01001','01002','01003','01004','01005','01007','01008','01009','01010','01011','01012','01013','01014','01020','01021','01022','01026','01027','01028','01029','01030','01031','01032','01033','01034','01035','01036','01037','01038','01039','01040','01041','01050','01053','01054','01056','01057','01059','01060','01061','01062','01063','01066','01068','01069','01070','01071','01072','01073','01074','01075','01077','01079','01080','01081','01082
>>
>> ERROR = Connection terminated
>> root@monetdb:/tmp#
>> 4) SQL
>>
>>
>> Dariusz
>>
>> Martin Kersten wrote:
>>> Hi Dariusz,
>>>
>>> A bug or a system limitation. It should at least never crash.
>>>
>>> How did you submit the query? To mclient? or mserver? or through
>>> a mapi libary call?
>>>
>>> I would have to look into the SQL parser. The underlying stream would
>>> expand upon need. It is, however, an interesting query. What kind of
>>> application generates it?
>>>
>>> regards, Martin
>>>
>>> ps. we should keep a profile of users to avoid asking platform
>>> details.
>>>
>>> dariuszs wrote:
>>>> Hi Martin,
>>>> Then I guess it's a bug. Please try running a query over 44k,
>>>> you'll get
>>>> MAPI = monetdb@localhost:50000
>>>> ACTION= read_line.
>>>> QUERY = select count(*) from plk100 WHERE c15 IN
>>>> ('00501','00544','01001','01002','01003'..........
>>>> ERROR = Connection terminated
>>>> Any query under 44k runs fine, so I'm assuming the limit is 64k
>>>> (query + other packet data)
>>>>
>>>> Thanks. Dariusz.
>>>>
>>>>
>>>>
>>>> Martin Kersten wrote:
>>>>> dariuszs wrote:
>>>>>
>>>>>> Hi,
>>>>>> Is there any limit on how big the sql query can be (in bytes)?
>>>>>> Thanks. Dariusz.
>>>>>>
>>>>>>
>>>>> As far as i am aware no.
>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>>
>>>>>> Download Intel® Parallel Studio Eval
>>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>>> proactively, and fine-tune applications for parallel performance.
>>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>>> _______________________________________________
>>>>>> MonetDB-users mailing list
>>>>>> MonetDB-users(a)lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/monetdb-users
>>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>> Download Intel® Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> MonetDB-users mailing list
>>>>> MonetDB-users(a)lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/monetdb-users
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>
>
>
>
I get the following error when trying to connect a MonetDB database with
'OpenOffice.org Database' through the ODBC driver.
[unixODBC][MonetDB][ODBC Driver 1.0]Client unable to establish connection
.ini-files used:
odbc.ini:
[MonetDB_User]
Description = Default MonetDB Data Source
Driver = MonetDB
Host = localhost
Port = 50000
Database = TestDB
User = monetdb
Password = monetdb
Debug =
odbcinst.ini
[MonetDB]
Description = MonetDB Driver
Driver =
Driver64 = /home/breplu/MonetDB/lib/libMonetODBC.so
Setup =
Setup64 = /home/breplu/MonetDB/lib/libMonetODBCs.so
UsageCount = 1
CPTimeout =
CPReuse =
MonetDB version: Feb2010 release
A ODBC connection between MySql and OpenOffice works correctly, so I don't
think the problem lies with OpenOffice.
Am I doing something wrong or is this a know issue with MonetDB?
Thanks in advance.
--
View this message in context: http://old.nabble.com/ODBC-connection-problem.-tp28364397p28364397.html
Sent from the monetdb-users mailing list archive at Nabble.com.
I'm guessing that this was meant to be "SMALLINT".
From: http://monetdb.cwi.nl/SQL/Documentation/SQL-Features.html
Feature ID Feature name S/N
B011-B017 Embedded Language support. Core SQL:1999 says that at least one of Embedded Ada, Embedded C, Embedded Cobol, Embedded Fortran, Embedded MUMPS, Embedded Pascal or Embedded PL/I 1 should be supported. N
E011 Numeric data types (FULL support) S
E011-01 INTEGER and SMELLIEST data types
^^^^^^^^^
I know I read that page before, funny I never noticed that.
(I have to admit, I did check the standard just to make sure it wasn't in there and I had just missed it all these years.)
I have seen a few database tables that had some really stinky data types, but I'm glad I never came across one that contained the smelliest. :-)
Steve
--- On Mon, 4/26/10, Mark Bucciarelli <mkbucc(a)gmail.com> wrote:
> From: Mark Bucciarelli <mkbucc(a)gmail.com>
> $ cd src/monet_2009Nov/
> $ find . -name "*sql*.y"
> ./sql/src/server/sql_parser.y
> $
>
> Well commented YACC source.
>
> I use that when I have a SQL question.
This file is not in any of the tarballs, including Nov2009.
Do you have to generate it?
If so, that would be a horrible way to document an external API:
1) Download source code.
2) Run lexical analyzer on source code.
3) Try to understand code comments.
4) Retry your query in the client application.
Is there another document somewhere?
If the comments are very good, maybe that could be quickly refined to become the official documentation.
Thanks,
Steve
Dear MonetDB users,
Is it all possible to grant the privilege of "creating tables" to some users in MonetDB? For example, something like "grant create table to user_name" or similar?
Thanks,
Min
Dear all,
I just want to address my question in last message in a more specific way. Actually I am wondering if I can grant privileges to creating local/global temporary tables to a normal user other than monetdb. And what is the complete list of priveleges known to MonetDB?
Thanks,
Min
