rlib-users

[Rlib-users] Rlib 1.1.5 Released

[Bob D. <bd...@si...>]

Hey all,

Chet and I are happy to announce the relase of RLIB 1.1.5 (still
beta...)

- rlib_add_parameter (chet)
- optional memory checking (chet)
- reports can span multiple pages (bob)
- fix problems w/ postgre and odbc driver (bob)
- ability to disable signal handling (chet)
- page footer formats correctly now (bob)
- pcode compilation fixes (chet, bob)
- better xml parsing and error checking (chet)
- surpress lines and hr's (bob)

Again.. special thanks to Everton Luis Berz.. for all of his bug
reports.. pretty soon we will have more examples thanks to him... 

Known problems:
	Number formatting w/ i18n still doesn't work
	HTML page footer might be not be correct

Please test it :)

- Bob

Re: [Rlib-users] Rlib 1.1.5 Released

[Bob D. <bd...@si...>]

Hym.....

Does the breaks bug exist in all database formats or just postgre?

On the subject of RLIB memory checking:

1) Did you compile rlib with/ --enable-memdebug ??

2) If a query fails to run rlib_execute will do nothing.. and return -1

so you should do some error checking for that... but we should keep a
state in RLIB and protect us from crashing/ getting confused..

hey Chet.. can you add a flag to the rlib struct.. and initially set it
to good.. in the add_datasource_* stuff.. if anything fails set it to
bad.. then in execute.. if it is bad just return -1.. but if it is good
execute.. and if execute has problems set it to bad... then in the
spool, rlib_get_output, ect.. make sure we are good before returning
stuff?

But.. you should be doing this anyway:

.
.
.
if(rlib_add_datasource_postgre($rlib, "pgsql", "host=localhost  
dbname=rlib_examples_latin user=postgres") == -1)
  echo "Could not connect to......"
else {
  rlib_add_query_as($rlib, "pgsql", $sql, "jobs");
  rlib_add_report($rlib, "jobs.xml");
  rlib_set_output_format_from_text($rlib, $format);
  if(rlib_execute($rlib) == -1) 
   echo "faild to run a query, bad xml or something..."
  else {
    header( rlib_get_content_type($rlib));
    rlib_spool($rlib);
  }
}
rlib_free($rlib);

- Bob

On Thu, 2003-12-04 at 08:21, Everton Luis Berz wrote:
> I think i found a bug on breaks when records that appears
> in detail repeats.  (1.1.4 has the bug too)
> 
> *** Example (working):
> Query result:
> Amazon  | 6 | Britney
> Amazon  | 1 | Everton
> Amazon  | 5 | John
> Hellion | 6 | Britney
> SICOM   | 4 | Andrew
> 
> Rlib result:  (company is the breakfield)
> Company: Amazon
>    6 Britney
>    1 Everton
>    5 John
> Company: Hellion
>    6 Britney
> Company: SICOM
>    4 Andrew
> 
> *** Example (bug)
> Query result:
> Amazon  | 6 | Britney
> Hellion | 6 | Britney
> SICOM   | 4 | Andrew
> 
> Rlib result:  (company is the breakfield)
> Company: Amazon
>    6 Britney
> Company: SICOM
>    4 Andrew
> 
> 
> Where is 'Hellion' break and detail?
> 
> 
> I'm sending new jobs.php (from examples), run it and
> you will see that one record does not appear.
> 
> 
> Other problem.. not serious..
> i think that's a problem on new memory checking because
> when i run a erroneous report (with sql syntax error) my
> computer break, hard disk craze, etc.. some minutes after this
> it's back to normal, but sometimes i need restart linux.
> 
> 
> thanks.
> 
> 
> Bob Doan escreveu:
> > Hey all,
> > 
> > Chet and I are happy to announce the relase of RLIB 1.1.5 (still
> > beta...)
> > 
> > - rlib_add_parameter (chet)
> > - optional memory checking (chet)
> > - reports can span multiple pages (bob)
> > - fix problems w/ postgre and odbc driver (bob)
> > - ability to disable signal handling (chet)
> > - page footer formats correctly now (bob)
> > - pcode compilation fixes (chet, bob)
> > - better xml parsing and error checking (chet)
> > - surpress lines and hr's (bob)
> > 
> > Again.. special thanks to Everton Luis Berz.. for all of his bug
> > reports.. pretty soon we will have more examples thanks to him... 
> > 
> > Known problems:
> > 	Number formatting w/ i18n still doesn't work
> > 	HTML page footer might be not be correct
> > 
> > Please test it :)
> > 
> > - Bob
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by OSDN's Audience Survey.
> > Help shape OSDN's sites and tell us what you think. Take this
> > five minute survey and you could win a $250 Gift Certificate.
> > http://www.wrgsurveys.com/2003/osdntech03.php?site=8
> > _______________________________________________
> > Rlib-users mailing list
> > Rli...@li...
> > https://lists.sourceforge.net/lists/listinfo/rlib-users
> > 
> 

Re: [Rlib-users] Rlib 1.1.5 Released

[Everton L. B. <ev...@fa...>]

Bob Doan escreveu:
> Hym.....
> 
> Does the breaks bug exist in all database formats or just postgre?
postgre and odbc postgre. mysql is ok.

> 
> On the subject of RLIB memory checking:
> 
> 1) Did you compile rlib with/ --enable-memdebug ??
No, just --disable-python. Must i enable memdebug ?

> 
> 2) If a query fails to run rlib_execute will do nothing.. and return -1
> 
> so you should do some error checking for that... but we should keep a
> state in RLIB and protect us from crashing/ getting confused..
> 
> hey Chet.. can you add a flag to the rlib struct.. and initially set it
> to good.. in the add_datasource_* stuff.. if anything fails set it to
> bad.. then in execute.. if it is bad just return -1.. but if it is good
> execute.. and if execute has problems set it to bad... then in the
> spool, rlib_get_output, ect.. make sure we are good before returning
> stuff?
> 
> But.. you should be doing this anyway:
> 
> .
> .
> .
> if(rlib_add_datasource_postgre($rlib, "pgsql", "host=localhost  
> dbname=rlib_examples_latin user=postgres") == -1)
>   echo "Could not connect to......"
> else {
>   rlib_add_query_as($rlib, "pgsql", $sql, "jobs");
>   rlib_add_report($rlib, "jobs.xml");
>   rlib_set_output_format_from_text($rlib, $format);
>   if(rlib_execute($rlib) == -1) 
>    echo "faild to run a query, bad xml or something..."
>   else {
>     header( rlib_get_content_type($rlib));
>     rlib_spool($rlib);
>   }
> }
> rlib_free($rlib);

I try putting "if's" like above and the problem persist.

> 
> - Bob
> 
> On Thu, 2003-12-04 at 08:21, Everton Luis Berz wrote:
> 
>>I think i found a bug on breaks when records that appears
>>in detail repeats.  (1.1.4 has the bug too)
>>
>>*** Example (working):
>>Query result:
>>Amazon  | 6 | Britney
>>Amazon  | 1 | Everton
>>Amazon  | 5 | John
>>Hellion | 6 | Britney
>>SICOM   | 4 | Andrew
>>
>>Rlib result:  (company is the breakfield)
>>Company: Amazon
>>   6 Britney
>>   1 Everton
>>   5 John
>>Company: Hellion
>>   6 Britney
>>Company: SICOM
>>   4 Andrew
>>
>>*** Example (bug)
>>Query result:
>>Amazon  | 6 | Britney
>>Hellion | 6 | Britney
>>SICOM   | 4 | Andrew
>>
>>Rlib result:  (company is the breakfield)
>>Company: Amazon
>>   6 Britney
>>Company: SICOM
>>   4 Andrew
>>
>>
>>Where is 'Hellion' break and detail?
>>
>>
>>I'm sending new jobs.php (from examples), run it and
>>you will see that one record does not appear.
>>
>>
>>Other problem.. not serious..
>>i think that's a problem on new memory checking because
>>when i run a erroneous report (with sql syntax error) my
>>computer break, hard disk craze, etc.. some minutes after this
>>it's back to normal, but sometimes i need restart linux.
>>
>>
>>thanks.
>>
>>
>>Bob Doan escreveu:
>>
>>>Hey all,
>>>
>>>Chet and I are happy to announce the relase of RLIB 1.1.5 (still
>>>beta...)
>>>
>>>- rlib_add_parameter (chet)
>>>- optional memory checking (chet)
>>>- reports can span multiple pages (bob)
>>>- fix problems w/ postgre and odbc driver (bob)
>>>- ability to disable signal handling (chet)
>>>- page footer formats correctly now (bob)
>>>- pcode compilation fixes (chet, bob)
>>>- better xml parsing and error checking (chet)
>>>- surpress lines and hr's (bob)
>>>
>>>Again.. special thanks to Everton Luis Berz.. for all of his bug
>>>reports.. pretty soon we will have more examples thanks to him... 
>>>
>>>Known problems:
>>>	Number formatting w/ i18n still doesn't work
>>>	HTML page footer might be not be correct
>>>
>>>Please test it :)
>>>
>>>- Bob
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by OSDN's Audience Survey.
>>>Help shape OSDN's sites and tell us what you think. Take this
>>>five minute survey and you could win a $250 Gift Certificate.
>>>http://www.wrgsurveys.com/2003/osdntech03.php?site=8
>>>_______________________________________________
>>>Rlib-users mailing list
>>>Rli...@li...
>>>https://lists.sourceforge.net/lists/listinfo/rlib-users
>>>
>>
> 


-- 
Everton Luis Berz
Nucleo de Sistemas :: FACCAT - Faculdades de Taquara
+55 51 541 6600 - R.624
ICQ 7807919

Re: [Rlib-users] Rlib 1.1.5 Released

[Bob D. <bd...@si...>]

On Thu, 2003-12-04 at 10:15, Everton Luis Berz wrote:
> Bob Doan escreveu:
> > Hym.....
> > 
> > Does the breaks bug exist in all database formats or just postgre?
> postgre and odbc postgre. mysql is ok.

Ok.. sounds like a input bug.. not a engine bug.. good :).. I'll set my
self up w/ your data in a bit and take a look

> 
> > 
> > On the subject of RLIB memory checking:
> > 
> > 1) Did you compile rlib with/ --enable-memdebug ??
> No, just --disable-python. Must i enable memdebug ?

Um.. not unless you are actually developing RLIB source :)

> I try putting "if's" like above and the problem persist.

My new guess is because of the failure we are freeing something we are
not supposed to.. could you try taking out the rlib_free and see if the
problem still exists? My guess is it won't.. let me know

- Bob

Re: [Rlib-users] Rlib 1.1.5 Released

[Everton L. B. <ev...@fa...>]

Bob Doan escreveu:
> On Thu, 2003-12-04 at 10:15, Everton Luis Berz wrote:
> 
> 
>>I try putting "if's" like above and the problem persist.
> 
> 
> My new guess is because of the failure we are freeing something we are
> not supposed to.. could you try taking out the rlib_free and see if the
> problem still exists? My guess is it won't.. let me know

Yes, still exists.

> 
> - Bob
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Rlib-users mailing list
> Rli...@li...
> https://lists.sourceforge.net/lists/listinfo/rlib-users
> 


-- 
Everton Luis Berz
Nucleo de Sistemas :: FACCAT - Faculdades de Taquara
+55 51 541 6600 - R.624
ICQ 7807919

Re: [Rlib-users] Rlib 1.1.5 Released

[Bob D. <bd...@si...>]

> > 
> > My new guess is because of the failure we are freeing something we are
> > not supposed to.. could you try taking out the rlib_free and see if the
> > problem still exists? My guess is it won't.. let me know
> 
> Yes, still exists.

Ok.. so I'm not good at guessing ;)

I'll try to reproduce it.. should be easy enough.. I'll let you know if
I can't

- Bob