Isjtar

mysql-woos

> the net.loadbang stuff gives me an immense error (see below) when i 

> press connect (the login arguments should be correct)

Immense indeed, although I think most of it is coming from the MySQL 

JDBC connector. It does highlight the problem, though: "Connection 

refused" - which suggests that the database is not running, or the 

host machine is not accepting TCP/IP connections.

> the net.loadbang stuff gives me an immense error (see below) when i  
> press connect (the login arguments should be correct)

Immense indeed, although I think most of it is coming from the MySQL  
JDBC connector. It does highlight the problem, though: "Connection  
refused" - which suggests that the database is not running, or the  
host machine is not accepting TCP/IP connections.

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.last.fm/music/cassiel
www.loadbang.net


thanks guys for the input, nice to have external developers 

we've reinstalled the database locally and found out it was the port 

now, there are largish chunks of text in the db that we're spitting 

with nice crashes as a result, tough these don't seem to be related 

i'm trying to convert the strings to a more manageable format, like 

connecting to fromsymbol > prepend set >message box causes a crash on 

limiting the strings with strcut(1000) makes the crashes more rare, 

but if i then connect to text object (with a clear first) makes it 

i'm sorry i can't be more specific, i'm trying al kinds of 

workarounds, but the problem keeps popping up in other places, like 

On Oct 13, 2007, at 11:50 PM, Nick Rothwell wrote:

> On 11 Oct 2007, at 19:14, isjtar wrote:

>> the net.loadbang stuff gives me an immense error (see below) when 

>> i press connect (the login arguments should be correct)

> Immense indeed, although I think most of it is coming from the 

> MySQL JDBC connector. It does highlight the problem, though: 

> "Connection refused" - which suggests that the database is not 

> running, or the host machine is not accepting TCP/IP connections.

thanks guys for the input, nice to have external developers  
responding so quickly.
we've reinstalled the database locally and found out it was the port  
number that was wrong.

now, there are largish chunks of text in the db that we're spitting  
out into max.
with nice crashes as a result, tough these don't seem to be related  
to length.
i'm trying to convert the strings to a more manageable format, like  
list.
connecting to fromsymbol > prepend set >message box causes a crash on  
some queries.
limiting the strings with strcut(1000) makes the crashes more rare,  
but if i then connect to text object (with a clear first) makes it  
crash more often again.
i'm sorry i can't be more specific, i'm trying al kinds of  
workarounds, but the problem keeps popping up in other places, like  
i'm pushing it forward.
any known probems with this?

>
> On 11 Oct 2007, at 19:14, isjtar wrote:
>
>> the net.loadbang stuff gives me an immense error (see below) when  
>> i press connect (the login arguments should be correct)
>
> Immense indeed, although I think most of it is coming from the  
> MySQL JDBC connector. It does highlight the problem, though:  
> "Connection refused" - which suggests that the database is not  
> running, or the host machine is not accepting TCP/IP connections.
>
> 	-- N.
>
>
> Nick Rothwell / Cassiel.com Limited
> www.cassiel.com
> www.myspace.com/cassieldotcom
> www.last.fm/music/cassiel
> www.loadbang.net
>
>
>


I have'nt had any problems like this with my work. But, maybe I am 

not pushing as much data as you are? Also I am doing a lot of 

preprocessing in Java so I am bypassing any potential Max limitations.

You might want to isolate the problem a bit. For example, try 

manually copying some data from the Mysql database into a message box 

and parsing it to see if you still have issues.

I know from personal experience that it can be hard to isolate issues 

in large projects, but still more info would be useful. First of all, 

which solution are you using? If you tried both are you getting the 

Without knowing more about your data and specifically the way you are 

processing it it is hard to say much else.

On Oct 15, 2007, at 1:14 PM, isjtar wrote:

> thanks guys for the input, nice to have external developers 

> we've reinstalled the database locally and found out it was the 

> now, there are largish chunks of text in the db that we're spitting 

> with nice crashes as a result, tough these don't seem to be related 

> i'm trying to convert the strings to a more manageable format, like 

> connecting to fromsymbol > prepend set >message box causes a crash 

> limiting the strings with strcut(1000) makes the crashes more rare, 

> but if i then connect to text object (with a clear first) makes it 

> i'm sorry i can't be more specific, i'm trying al kinds of 

> workarounds, but the problem keeps popping up in other places, like 

> On Oct 13, 2007, at 11:50 PM, Nick Rothwell wrote:

>> On 11 Oct 2007, at 19:14, isjtar wrote:

>>> the net.loadbang stuff gives me an immense error (see below) when 

>>> i press connect (the login arguments should be correct)

>> Immense indeed, although I think most of it is coming from the 

>> MySQL JDBC connector. It does highlight the problem, though: 

>> "Connection refused" - which suggests that the database is not 

>> running, or the host machine is not accepting TCP/IP connections.

Hi isjtar-
I have'nt had any problems like this with my work. But, maybe I am  
not pushing as much data as you are? Also I am doing a lot of  
preprocessing in Java so I am bypassing any potential Max limitations.

You might want to isolate the problem a bit. For example, try  
manually copying some data from the Mysql database into a message box  
and parsing it to see if you still have issues.

I know from personal experience that it can be hard to isolate issues  
in large projects, but still more info would be useful. First of all,  
which solution are you using? If you tried both are you getting the  
same behavior?

Without knowing more about your data and specifically the way you are  
processing it it is hard to say much else.

> thanks guys for the input, nice to have external developers  
> responding so quickly.
> we've reinstalled the database locally and found out it was the  
> port number that was wrong.
>
> now, there are largish chunks of text in the db that we're spitting  
> out into max.
> with nice crashes as a result, tough these don't seem to be related  
> to length.
> i'm trying to convert the strings to a more manageable format, like  
> list.
> connecting to fromsymbol > prepend set >message box causes a crash  
> on some queries.
> limiting the strings with strcut(1000) makes the crashes more rare,  
> but if i then connect to text object (with a clear first) makes it  
> crash more often again.
> i'm sorry i can't be more specific, i'm trying al kinds of  
> workarounds, but the problem keeps popping up in other places, like  
> i'm pushing it forward.
> any known probems with this?
>
> thanks again
>
>
> isjtar
>
>
> On Oct 13, 2007, at 11:50 PM, Nick Rothwell wrote:
>
>>
>> On 11 Oct 2007, at 19:14, isjtar wrote:
>>
>>> the net.loadbang stuff gives me an immense error (see below) when  
>>> i press connect (the login arguments should be correct)
>>
>> Immense indeed, although I think most of it is coming from the  
>> MySQL JDBC connector. It does highlight the problem, though:  
>> "Connection refused" - which suggests that the database is not  
>> running, or the host machine is not accepting TCP/IP connections.
>>
>> 	-- N.
>>
>>
>> Nick Rothwell / Cassiel.com Limited
>> www.cassiel.com
>> www.myspace.com/cassieldotcom
>> www.last.fm/music/cassiel
>> www.loadbang.net
>>
>>
>>
>
>
>


at the moment we're trying with the loadbang external, but we're 

about the isolating... yes I know you can't help me like this, i'm 

looking but it keeps popping up all over the place, hence the general 

thing is it's not really my project, i'm just helping out. it's a 

public db with people putting texts and photos in it.

the texts are a mess, encoded in many different editors etc.

next thing will be to tackle the formatting.

the person running it is actually thinking of editing all by hand in 

putting into colls, but that's way to painful imo. i'll dive back in 

thanks for the help, i'll post as soon as i can put my finger on it.

On Oct 15, 2007, at 10:36 PM, MarkDavid Hosale wrote:

> I have'nt had any problems like this with my work. But, maybe I am 

> not pushing as much data as you are? Also I am doing a lot of 

> preprocessing in Java so I am bypassing any potential Max limitations.

> You might want to isolate the problem a bit. For example, try 

> manually copying some data from the Mysql database into a message 

> box and parsing it to see if you still have issues.

> I know from personal experience that it can be hard to isolate 

> issues in large projects, but still more info would be useful. 

> First of all, which solution are you using? If you tried both are 

> Without knowing more about your data and specifically the way you 

> are processing it it is hard to say much else.

> On Oct 15, 2007, at 1:14 PM, isjtar wrote:

>> thanks guys for the input, nice to have external developers 

>> we've reinstalled the database locally and found out it was the 

>> now, there are largish chunks of text in the db that we're 

>> with nice crashes as a result, tough these don't seem to be 

>> i'm trying to convert the strings to a more manageable format, 

>> connecting to fromsymbol > prepend set >message box causes a crash 

>> limiting the strings with strcut(1000) makes the crashes more 

>> rare, but if i then connect to text object (with a clear first) 

>> i'm sorry i can't be more specific, i'm trying al kinds of 

>> workarounds, but the problem keeps popping up in other places, 

>> On Oct 13, 2007, at 11:50 PM, Nick Rothwell wrote:

at the moment we're trying with the loadbang external, but we're  
still trying all kinds of things.
about the isolating... yes I know you can't help me like this, i'm  
looking but it keeps popping up all over the place, hence the general  
question.
thing is it's not really my project, i'm just helping out. it's a  
public db with people putting texts and photos in it.
the texts are a mess, encoded in many different editors etc.
next thing will be to tackle the formatting.
the person running it is actually thinking of editing all by hand in  
putting into colls, but that's way to painful imo. i'll dive back in  
tomorrow.
thanks for the help, i'll post as soon as i can put my finger on it.

> Hi isjtar-
> I have'nt had any problems like this with my work. But, maybe I am  
> not pushing as much data as you are? Also I am doing a lot of  
> preprocessing in Java so I am bypassing any potential Max limitations.
>
> You might want to isolate the problem a bit. For example, try  
> manually copying some data from the Mysql database into a message  
> box and parsing it to see if you still have issues.
>
> I know from personal experience that it can be hard to isolate  
> issues in large projects, but still more info would be useful.  
> First of all, which solution are you using? If you tried both are  
> you getting the same behavior?
>
> Without knowing more about your data and specifically the way you  
> are processing it it is hard to say much else.
>
> hope this helps-
> md
>
> On Oct 15, 2007, at 1:14 PM, isjtar wrote:
>
>> thanks guys for the input, nice to have external developers  
>> responding so quickly.
>> we've reinstalled the database locally and found out it was the  
>> port number that was wrong.
>>
>> now, there are largish chunks of text in the db that we're  
>> spitting out into max.
>> with nice crashes as a result, tough these don't seem to be  
>> related to length.
>> i'm trying to convert the strings to a more manageable format,  
>> like list.
>> connecting to fromsymbol > prepend set >message box causes a crash  
>> on some queries.
>> limiting the strings with strcut(1000) makes the crashes more  
>> rare, but if i then connect to text object (with a clear first)  
>> makes it crash more often again.
>> i'm sorry i can't be more specific, i'm trying al kinds of  
>> workarounds, but the problem keeps popping up in other places,  
>> like i'm pushing it forward.
>> any known probems with this?
>>
>> thanks again
>>
>>
>> isjtar
>>
>>
>> On Oct 13, 2007, at 11:50 PM, Nick Rothwell wrote:
>>
>>>
>>> On 11 Oct 2007, at 19:14, isjtar wrote:
>>>
>>>> the net.loadbang stuff gives me an immense error (see below)  
>>>> when i press connect (the login arguments should be correct)
>>>
>>> Immense indeed, although I think most of it is coming from the  
>>> MySQL JDBC connector. It does highlight the problem, though:  
>>> "Connection refused" - which suggests that the database is not  
>>> running, or the host machine is not accepting TCP/IP connections.
>>>
>>> 	-- N.
>>>
>>>
>>> Nick Rothwell / Cassiel.com Limited
>>> www.cassiel.com
>>> www.myspace.com/cassieldotcom
>>> www.last.fm/music/cassiel
>>> www.loadbang.net
>>>
>>>
>>>
>>
>>
>>
>


> db with people putting texts and photos in it.

> the texts are a mess, encoded in many different editors etc.

> next thing will be to tackle the formatting.

From my own experience with Max and MySQL database (not using the Java 

stuff but my own mysql external) and from similar experience with an 

external to receive emails in Max I can tell you that some crashes just 

seem to be caused by Max not liking certain characters.

So when you download from a database and you don't know what's in there 

you might end up crashing when you just display that data in a message 

box, for example. In my case (with the emails) it helped to have the 

external output the complete email as one symbol. I then passed that 

symbol to another external that did some processing with it. However, 

trying to use [print] in order to see what I got crashed Max quite 

Also, you might get commas and semicolons and other fun stuff back from 

your mysql queries and have to properly deal with them (in case the Java 

DB stuff doesn't do that for you by - for example - putting everything 

into one symbol or properly escaping it).

On the positive side, I have used Max and databases for two rather big 

projects now and it always worked smoothly as long as you have control 

over what people put in the database. Some strange chracters in there 

isjtar wrote:
> db with people putting texts and photos in it.
> the texts are a mess, encoded in many different editors etc.
> next thing will be to tackle the formatting.

 From my own experience with Max and MySQL database (not using the Java 
stuff but my own mysql external) and from similar experience with an 
external to receive emails in Max I can tell you that some crashes just 
seem to be caused by Max not liking certain characters.
So when you download from a database and you don't know what's in there 
you might end up crashing when you just display that data in a message 
box, for example. In my case (with the emails) it helped to have the 
external output the complete email as one symbol. I then passed that 
symbol to another external that did some processing with it. However, 
trying to use [print] in order to see what I got crashed Max quite 
reliably.
Also, you might get commas and semicolons and other fun stuff back from 
your mysql queries and have to properly deal with them (in case the Java 
DB stuff doesn't do that for you by - for example - putting everything 
into one symbol or properly escaping it).

On the positive side, I have used Max and databases for two rather big 
projects now and it always worked smoothly as long as you have control 
over what people put in the database. Some strange chracters in there 
can really ruin your day!

This is almost certainly due to grief in the Max world rather than 

the Java world. It's probably best solved in Java (the loadbang.net 

MySQL package is documented and can be used in other Java code). 

Failing that, you may be able to work round some of the problems 

using MySQL functions in the SQL statements, although I'm not that 

> now, there are largish chunks of text in the db that we're spitting  
> out into max.
> with nice crashes as a result, tough these don't seem to be related  
> to length.

This is almost certainly due to grief in the Max world rather than  
the Java world. It's probably best solved in Java (the loadbang.net  
MySQL package is documented and can be used in other Java code).  
Failing that, you may be able to work round some of the problems  
using MySQL functions in the SQL statements, although I'm not that  
familiar with them.

MySQL woos