World: r3wp

Will: I'll have to ask Reichart.

Please 8P

Guys, what do you think about Tim Johnson's ml remark? Could we help 
him somehow?

-----------------------------------

I've been using mysql-protocol (Mysql Scheme) and cgi for many years 
now. I 

really like it, but I think that /command would bring some advantages, 
if
it can directly access the "C" API for MySQL.


Example: Using the mysql scheme on a tcp/ip connection, I have to 
code

the escaping of special characters for insert and updates and code 
the
unescaping of special characters for retrieval. 


Using the C API from other scripting languages, the mysql_real_escape_string()
function handles the escaping _appropriate_ to the version, and
queries are similarly unescaped.

Isn't REBOL fast enough for most operations in regards to MySQL? 
Wouldn't it be sufficient to write such escaping fun in REBOL?

about escaping, Nenad's driver has such functions already, so i don't 
see that as an advantage for the native driver. Qtask has a native 
driver too (for speed reason with large record sets), but remember 
that when you use the mysql c library either your app has to be GPL 
or you need a license from MySQL (Qtask has a license).

I have a mysql wrapper that I use in production but haven't released 
because it need cleaning and docs, but if there is interest I could 
release for testing as is. id does things like:

print .db/get/all/sort/debug [mailing/m mailingLog/ml] [ml.dc m.email 
ml.url] [{ml._mailing=m.id}] [m.email asc ml.dc desc]

SELECT `ml`.`dc`,`m`.`email`,`ml`.`url` FROM `mailing` `m`,`mailingLog` 
`ml` WHERE ml._mailing=m.id ORDER BY `m`.`email`,`ml`.`dc` DESC
print .db/set/debug 'mailing 12 reduce['active false] 
UPDATE `mailing` SET `active`=0 WHERE id=12.0

print .db/get/all/flat/debug '_node_tree [_node _media] [{_tree=? 
AND _issue=?} 5443 22]

SELECT `_node`,`_media` FROM `_node_tree` WHERE _tree='5443' AND 
_issue='22'
..

Will, that would be sweet.

Gabriele, I thought you only needed a license if you are releasing 
your software ....

graham, i'm not entirely sure, in principle the GPL2 is as you say, 
however i'm not sure if MySQL has a different interpretation here. 
iirc the GPL3 states that being a server for users is the same as 
releasing the software.

No, that's the Affero GPL.

They took that clause out of the regular GPL3 during the review process, 
after many protested it.

So, looks like you didn't need a license

Qtask? no, it does, because you can also put qtask on your own server.

Has that happened yet?

i don't think you can buy it right now, and the focus has shifted 
to the SaaS model, but otherwise there are no major tech obstacles 
iirc. ask reichart for more details, i'm not really up to date on 
the marketing/sales stuff :)

He's often mentioned that they are considering open sourcing qtask 
in which again the license was not needed!

well, not all of qtask, but again i don't really know. i know they 
talked to mysql and all is fine. i'm not implying they paid or are 
paying money, since i don't know. my point is that Qtask has permission 
from MySQL to do what they do, while you may not if you were to use 
the same code. Is that more clear?

Why didn't qtask use postgresql instead??

Why is the world flat?

because of a limited viewpoint

I agree, your viewpoint wasn't economics....

With two open source databases to choose from of approximately similar 
functionality and stability, it is hard to understand why one would 
choose the one that has the restrictive license ... I can only imagine 
it is a mind share thing.

James, thanks for your interest, I' ll upload it in a couple days 
8)

Thanks.

Why wouldn't Qtask want to talk to Postgres too if they had chosen 
it?

Qtask might do this in the future...

Never used mysql before .. and just downloaded Nenad's driver.

Getting this ...

>> insert db "select * from patientrecord"
== none
>> result: copy db
** Script Error: Invalid argument: 0000-00-00
** Where: convert-types
** Near: change at row 3 to
>>

looks like some of the patient records have 0000-00-00 as the date 
of birth in them.

ok, this works round it

 insert db "select cast( birthdate as char) from patientrecord"

ummm.. how do you do a select on a field where the field name has 
a space in it?

Why would anyone put a space in a field name??

docs say \_ is a space

>> insert db "select middle\_name from patientrecord"

** User Error: ERROR 1064 : You have an error in your SQL syntax; 
check the manual that corresponds to your MySQL server ve
rsion for th...
** Near: insert db "select middle\_name from patientrecord"

ok, worked it out

 insert db "select `middle name` from patientrecord"

MySQL driver v1.2.1 released. See more at http://softinnov.org

Thanks for fixing the date zero error.

Thank you Dock!

For a long time, I was reluctant to change the date zero behaviour 
(error throwing), because this "feature" of MySQL look, to me,  like 
very bad design. But recently, I hit the problem too when I inserted 
badly formed dates in a table and wasn't able to read the records 
anymore with my driver.

Version 1.2.1 re-released. There was a small error in the 'name-fields 
function preventing it from working. Thanks to Will for reporting 
it.

James: sorry for the delay, still not found time for docs but her 
it is "as is.."  /debug is your friend, get started, load Dock driver 
, then load  http://reboot.ch/rebol/mysql-wrapper.txtthen:
;set a list of connections:
.db/databases: [
  ;local
  mydb1.local mysql://user:[password-:-127-:-0-:-0-:-1]/mydb1
  mydb2.local mysql://user:[password-:-127-:-0-:-0-:-1]/mydb2

  ;online
  mydb1 mysql://user:[password-:-127-:-0-:-0-:-1]:3307/mydb1
  mydb2 mysql://user:[password-:-127-:-0-:-0-:-1]:3307/mydb2
]
;use a db (if not open will open it automatically):	
.db/use 'mydb1

Thanks Will.

.

I've just upload a new experimental 1.3 version of MySQL driver supporting 
mutiple queries, stored procedures and multiple result sets. Reading 
mutiple results is done by calling COPY for each result. Download 
at http://softinnov.org/tmp/mysql-protocol-41.r

Keep in mind that if you're using SEND-SQL, it already does a implicit 
COPY.

It should be considered as a early beta, so test it well before using.

good news!

Thank Gabriele for keep pushing me. ;-)

Thank you! 8-))

the above new version seems to work fine for simple tests, apart 
from the issues Nenad has already listed.

this is going to be very useful :-)