libopendbx-devel — Help and discussion about OpenDBX

Re: [opendbx] man pages

[OpenDBX d. l. <lib...@li...>]

On Friday 13 June 2008 15:08:37 OpenDBX devel list wrote:
> Yes, I have docbook-2x installed and I have all the *.3 files in /doc.
> Know, what I have to do to include this in man pages. I am using ubuntu. I
> think I should include the path to /etc/manpath.config but I am not sure.

If the man pages are generated, the scripts generated by autoconf/automake put 
them into the filesystem automatically. Same as the binaries.

The problem you might face is that you may only call

./configure --with-backends="..."

This places everything (header files, libraries, man pages, etc) 
in /usr/local/ by default. If you call

./configure --prefix=/usr --with-backends="..."

instead, libraries are in /usr/lib, headers in /usr/include and man pages 
in /usr/share/man and everything should be found out of the box.


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] odbx_init vs odbx_bind performance

[OpenDBX d. l. <lib...@li...>]

On Fri, Jun 13, 2008 at 3:46 AM, OpenDBX devel list <
lib...@li...> wrote:

> Hi Mariano
>
> > So, my question is, which are the costs (in time) associated with both
> > functions? I mean, for each user (user of the application, not database
> > user) that uses the web app I can't do a bind and an init or should I do
> an
> > odbx_init only once for ALL users and then do a single bind per user?
>
> You need to call odbx_init() and an associated odbx_bind() as many times as
> you need different (!) connections because each connections needs its own
> datastructures created by odbx_init().
>


You are wright. I forgot that.


>
> To speed things up in web environments it would be a good idea to have a
> pool
> of already open connections. They should be created when they are first
> requested and given back to the pool after the script is done. New requests
> can be satisfied from pooled connection if they use the same backend, host,
> port, database, username, password and bind method. There's one pitfall:
> Some
> options can only be changed between the odbx_init() and the odbx_bind()
> call
> and that wouldn't be possible any more.
>


Norbert: Thanks for the data and help, you give us not only for openDBX but
also for our personal problems.
Yes, we have already think about having a connection pool to do exactly what
you said. However we didn't realize about that pitfall. We will keep it in
mind.





>
> Regards,
>
>
> Norbert
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

Re: [opendbx] man pages

[OpenDBX d. l. <lib...@li...>]

Yes, I have docbook-2x installed and I have all the *.3 files in /doc. Know,
what I have to do to include this in man pages. I am using ubuntu. I think I
should include the path to /etc/manpath.config but I am not sure.

The same hapens if I install openDBX from bianries ?

thanks

On Fri, Jun 13, 2008 at 3:12 AM, OpenDBX devel list <
lib...@li...> wrote:

> Hi Mariano
>
> > I was trying to generate the man pages for openDBX. I don't know how to
> do
> > it. I am newbie with this so probably I am doing something wrong. I tried
> > to run "make man" in the root directory of openDBX. Then I also tried in
> > /doc the same command, but no lucky.
> >
> > How can I generate man pages and entries for openDBX?
>
> You need the docbook-2x package. The ./configure script will automatically
> detect its presents and will generate the man pages from the docbook XML
> file
> in the doc/ directory. If you don't have this package installed,
> the ./configure will warn you that the man pages won't be generated.
>
> Regards,
>
>
> Norbert
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

Re: [opendbx] odbx_init vs odbx_bind performance

[OpenDBX d. l. <lib...@li...>]

Hi Mariano

> So, my question is, which are the costs (in time) associated with both
> functions? I mean, for each user (user of the application, not database
> user) that uses the web app I can't do a bind and an init or should I do an
> odbx_init only once for ALL users and then do a single bind per user?

You need to call odbx_init() and an associated odbx_bind() as many times as 
you need different (!) connections because each connections needs its own 
datastructures created by odbx_init().

To speed things up in web environments it would be a good idea to have a pool 
of already open connections. They should be created when they are first 
requested and given back to the pool after the script is done. New requests 
can be satisfied from pooled connection if they use the same backend, host, 
port, database, username, password and bind method. There's one pitfall: Some 
options can only be changed between the odbx_init() and the odbx_bind() call 
and that wouldn't be possible any more.

Regards,


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] man pages

[OpenDBX d. l. <lib...@li...>]

Hi Mariano

> I was trying to generate the man pages for openDBX. I don't know how to do
> it. I am newbie with this so probably I am doing something wrong. I tried
> to run "make man" in the root directory of openDBX. Then I also tried in
> /doc the same command, but no lucky.
>
> How can I generate man pages and entries for openDBX?

You need the docbook-2x package. The ./configure script will automatically 
detect its presents and will generate the man pages from the docbook XML file 
in the doc/ directory. If you don't have this package installed, 
the ./configure will warn you that the man pages won't be generated.

Regards,


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

[opendbx] odbx_init vs odbx_bind performance

[OpenDBX d. l. <lib...@li...>]

Hi!

I have some questions about performance to people who have already
implemented openDBX in real projects. As I told you, we are developing a
smalltalk wrapper of openDBX. This wrapper will probably be used from a web
application. In this architecture I'll probably have one and only one user
to the database and only one database.

So, my question is, which are the costs (in time) associated with both
functions? I mean, for each user (user of the application, not database
user) that uses the web app I can't do a bind and an init or should I do an
odbx_init only once for ALL users and then do a single bind per user?

I ask you this because our software will support certain API so that to be
used from other place and in this API there is one only method to connect to
database, so, perhaps, for us its easier to do a bind and an init per user.
But, if this has associated high costs, we could think other solution.

Thanks,

Mariano

[opendbx] man pages

[OpenDBX d. l. <lib...@li...>]

Hi everybody!

I was trying to generate the man pages for openDBX. I don't know how to do
it. I am newbie with this so probably I am doing something wrong. I tried to
run "make man" in the root directory of openDBX. Then I also tried in /doc
the same command, but no lucky.

How can I generate man pages and entries for openDBX?

very thanks,

Mariano

Re: [opendbx] Version 1.3.10 released

[OpenDBX d. l. <lib...@li...>]

EXCELLENT!!!!! What a great new. We really appreciate this.

I will test it as soon I as can so that to give you my feedback (fuck, I
have to use windows :( )

Thanks for this release.

Mariano

On Thu, Jun 12, 2008 at 6:52 PM, OpenDBX devel list <
lib...@li...> wrote:

> Dear OpenDBX users
>
> This release is a great leap forward towards bringing the OpenDBX library
> to
> the Windows platform. It compiles now on Windows NT based operating systems
> using either the Cygwin or MinGW environment. The library specification was
> also improved and doesn't allow the backends to return errors any more if
> odbx_result() or odbx_row_fetch() is called once more after they already
> returned DONE.
>
> With adding the Conn::finish(), Result::finish() and Lob::close() methods,
> the
> C++ API is now considered complete. These methods clean up their objects
> and
> are allowed to throw exceptions in case of errors which destructors aren't.
> Simplifying the API was continued by making parameters optional as much as
> possible. Last but not least the C++ API contains now inline documentation
> in
> Javadoc format.
>
> http://www.linuxnetworks.de/doc/index.php/OpenDBX/Download
>
>
> Norbert
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

[opendbx] Version 1.3.10 released

[OpenDBX d. l. <lib...@li...>]

Dear OpenDBX users

This release is a great leap forward towards bringing the OpenDBX library to 
the Windows platform. It compiles now on Windows NT based operating systems 
using either the Cygwin or MinGW environment. The library specification was 
also improved and doesn't allow the backends to return errors any more if 
odbx_result() or odbx_row_fetch() is called once more after they already 
returned DONE. 

With adding the Conn::finish(), Result::finish() and Lob::close() methods, the 
C++ API is now considered complete. These methods clean up their objects and 
are allowed to throw exceptions in case of errors which destructors aren't. 
Simplifying the API was continued by making parameters optional as much as 
possible. Last but not least the C++ API contains now inline documentation in 
Javadoc format.

http://www.linuxnetworks.de/doc/index.php/OpenDBX/Download


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] Problems with multiple statments

[OpenDBX d. l. <lib...@li...>]

On Wed, Jun 4, 2008 at 3:36 PM, OpenDBX devel list <
lib...@li...> wrote:

> Hi Mariano
>
> > I am trying to do some things with the multiple statments feature. To do
> > this, I am using odbx_set_option(). This function is like this:
> >
> > *int odbx_set_option( odbx_t* handle, unsigned int option, void* value )*
> >
> > 1) mysql:
> >
> > with 0: I have and error not when I set the option, but when I try to
> > execute the query: "You have an error in your SQL syntax; check the
> manual
> > that corresponds to your MySQL server version for the right syntax to use
> > near '';   "   This sounds logic because I am disabling this option.
> >
> > with 1: same error. This is ilogic.
>
> Which version of MySQL do you use?
> When you compile the OpenDBX library, you can see if HAVE_MYSQL_NEXT_RESULT
> is
> defined in config.in.
>


I am using MySQL 5



>
> > 2) postgresql:
> >
> > with 0:  I have the error ODBX_ERR_OPTWR which message es "Setting option
> > failed".
> > with 1 or X > 1: No error. Works fine the query.
> >
> > If I see pgsql_basic.c, function pgsql_odbx_set_option I see the case of
> > multiple statements and it is like this:
> >
> >         case ODBX_OPT_MULTI_STATEMENTS:
> >
> >             if( *((int*) value) ) { return ODBX_ERR_SUCCESS; }
> >             break;
> >
> > So, if it is 1 or any other value distinct from zero, no problem, It does
> > nothing and return success. But, if there is zero it does a break and
> then
> > goes out of the switch and it returns -ODBX_ERR_OPTWR; In fact, an error.
> >
> > So, my question is, why is like this? The only thing I thought is that
> > perhaps Postgresql always accept multiple statements and cannot be
> disable,
> > so, if I try to do this, I will have an error.
> >
> > Ahh and the multiple statements works fine in this case.
>
> You are right, PostgreSQL doesn't allow disabling support for multiple
> statements. Thus, you get this error.
>
> Furthermore, the name of odbx_get_option() is a little bit confusing, as
> this
> function tells you if certain options are supported. The correct code to
> set
> options would be:


Yes. I think it's a bit confusing. I thought the function odbx_get_option()
returns the actual value that is set, not asking if that is supported.


>
>
> int value;
> int opt = ODBX_OPT_MULTI_STATEMENTS;
>
> if( odbx_get_option( handle, opt, (void*) &value ) ) == ODBX_ERR_SUCCESS )
> {
>        if( value == ODBX_ENABLE )
>        {
>                if( odbx_set_option( handle, opt, (void*) &value ) ) ==
> ODBX_ERR_SUCCESS )
>                {
>                        // multiple statements are possible and enabled
>                }
>        }
> }
>
> This could also produce correct results for your MySQL case.


Ok. Seeing this code, I realize I was using wrong this two functions. As
soon as I could I'll probe it just like this.


>
>
> Generally speaking, options are expected to be enabled not disabled. The
> disabled state is the default if possible.
>
>
ok


>
> Norbert


Thanks!

Mariano


>
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

Re: [opendbx] Wiki and constants

[OpenDBX d. l. <lib...@li...>]

On Wed, Jun 4, 2008 at 3:52 PM, OpenDBX devel list <
lib...@li...> wrote:

> Hi Mariano
>
> > And then we can also do this with the specific options. We can put this
> > columns: constant name, real value, explication. Like this:
> >
> > ODBX_OPT_MULTI_STATEMENTS ; 0x0020; Enables the database server to accept
> > multiple statements in one query string sent via
> > odbx_query<
> http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_query
> >>() if the value of value is set to ODBX_ENABLE. Although, it might be
> > possible to disable it by setting it to ODBX_DISABLE.
> >
> > Do you think this would be useful for other than just us? If you want, I
> > can help you with this. Just tell me what you think about it.
>
> You belong to the very rare species of implementors who build a database
> API
> in another language using the OpenDBX library. Almost all other users are
> likely to create C or C++ applications so they don't need this information.


I supposed that.


>
> Furthermore I try to encourage all developers to use the constants instead
> of
> the real values as this greatly improves the readability.
>

Completely agree with you on using constants instead of the real values



>
> In your case, the easiest thing is to open the opendbx/api.h file and look
> for
> the value of the required constant.
>

yes yes.


>
> > And of course, we should replace each place in the wiki where an error is
> > explained, for a link to the constants page or something like this.
>
> The Wiki pages are automatically generated from the docbook XML which also
> generates the man pages. A description of the possible errors is expected
> in
> the man pages, so for a unified source of documentation it's not a good
> idea.
>

I didn't know this. Sounds logic.

thanks,

Mariano



>
>
> Norbert
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

Re: [opendbx] Wiki and constants

[OpenDBX d. l. <lib...@li...>]

Hi Mariano

> And then we can also do this with the specific options. We can put this
> columns: constant name, real value, explication. Like this:
>
> ODBX_OPT_MULTI_STATEMENTS ; 0x0020; Enables the database server to accept
> multiple statements in one query string sent via
> odbx_query<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_query
>>() if the value of value is set to ODBX_ENABLE. Although, it might be
> possible to disable it by setting it to ODBX_DISABLE.
>
> Do you think this would be useful for other than just us? If you want, I
> can help you with this. Just tell me what you think about it.

You belong to the very rare species of implementors who build a database API 
in another language using the OpenDBX library. Almost all other users are 
likely to create C or C++ applications so they don't need this information. 
Furthermore I try to encourage all developers to use the constants instead of 
the real values as this greatly improves the readability.

In your case, the easiest thing is to open the opendbx/api.h file and look for 
the value of the required constant.

> And of course, we should replace each place in the wiki where an error is
> explained, for a link to the constants page or something like this.

The Wiki pages are automatically generated from the docbook XML which also 
generates the man pages. A description of the possible errors is expected in 
the man pages, so for a unified source of documentation it's not a good idea.


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] Problems with multiple statments

[OpenDBX d. l. <lib...@li...>]

Hi Mariano

> I am trying to do some things with the multiple statments feature. To do
> this, I am using odbx_set_option(). This function is like this:
>
> *int odbx_set_option( odbx_t* handle, unsigned int option, void* value )*
>
> 1) mysql:
>
> with 0: I have and error not when I set the option, but when I try to
> execute the query: "You have an error in your SQL syntax; check the manual
> that corresponds to your MySQL server version for the right syntax to use
> near '';   "   This sounds logic because I am disabling this option.
>
> with 1: same error. This is ilogic.

Which version of MySQL do you use?
When you compile the OpenDBX library, you can see if HAVE_MYSQL_NEXT_RESULT is 
defined in config.in.

> 2) postgresql:
>
> with 0:  I have the error ODBX_ERR_OPTWR which message es "Setting option
> failed".
> with 1 or X > 1: No error. Works fine the query.
>
> If I see pgsql_basic.c, function pgsql_odbx_set_option I see the case of
> multiple statements and it is like this:
>
>         case ODBX_OPT_MULTI_STATEMENTS:
>
>             if( *((int*) value) ) { return ODBX_ERR_SUCCESS; }
>             break;
>
> So, if it is 1 or any other value distinct from zero, no problem, It does
> nothing and return success. But, if there is zero it does a break and then
> goes out of the switch and it returns -ODBX_ERR_OPTWR; In fact, an error.
>
> So, my question is, why is like this? The only thing I thought is that
> perhaps Postgresql always accept multiple statements and cannot be disable,
> so, if I try to do this, I will have an error.
>
> Ahh and the multiple statements works fine in this case.

You are right, PostgreSQL doesn't allow disabling support for multiple 
statements. Thus, you get this error.

Furthermore, the name of odbx_get_option() is a little bit confusing, as this 
function tells you if certain options are supported. The correct code to set 
options would be:

int value;
int opt = ODBX_OPT_MULTI_STATEMENTS;

if( odbx_get_option( handle, opt, (void*) &value ) ) == ODBX_ERR_SUCCESS )
{
	if( value == ODBX_ENABLE )
	{
		if( odbx_set_option( handle, opt, (void*) &value ) ) == ODBX_ERR_SUCCESS )
		{
			// multiple statements are possible and enabled
		}
	}
}

This could also produce correct results for your MySQL case.

Generally speaking, options are expected to be enabled not disabled. The 
disabled state is the default if possible.


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

[opendbx] Wiki and constants

[OpenDBX d. l. <lib...@li...>]

Hi! Me again. Now I have an idea. We (the team that is using openDBX from
Smalltalk) really needs the API. The client of openDBX in this case is not
another C program. So, as we are not developing in a C environment, it is
difficult for us to see which are the values of some constants for instance.

Because of that I think that perhaps it could be a good idea to have a wiki
page of constants. Suppose I have the lists of the error. I can have some
table with this columns: error constant name, error message , erro
explication.

Example:

ODBX_ERR_OPTWR ; Setting option failed ; Setting the option failed for
various reasons. It's most likely that the value passed via *value* didn't
match the range of values expected by the backend or the native database
library

ODBX_ERR_RESULT ; Waiting for result failed; Waiting for a response from the
server failed because the connection was lost


And then we can also do this with the specific options. We can put this
columns: constant name, real value, explication. Like this:

ODBX_OPT_MULTI_STATEMENTS ; 0x0020; Enables the database server to accept
multiple statements in one query string sent via
odbx_query<http://www.linuxnetworks.de/doc/index.php/OpenDBX/API/odbx_query>()
if the value of value is set to ODBX_ENABLE. Although, it might be possible
to disable it by setting it to ODBX_DISABLE.


And of course, we should replace each place in the wiki where an error is
explained, for a link to the constants page or something like this.

Do you think this would be useful for other than just us? If you want, I can
help you with this. Just tell me what you think about it.

cheers,

mariano

[opendbx] Problems with multiple statments

[OpenDBX d. l. <lib...@li...>]

Hi everybody,

I am trying to do some things with the multiple statments feature. To do
this, I am using odbx_set_option(). This function is like this:

*int odbx_set_option( odbx_t* handle, unsigned int option, void* value )*

In this cases, value should be ODBX_DISABLE (0) or ODBX_ENABLE (1) and
option should be ODBX_OPT_MULTI_STATEMENTS (0x0020 in hexa or 32 in
decimal). I am trying sending to this function 32 to option and 1 or 0 to
value. I test it with postgresql and mysql. These are the results:



1) mysql:

with 0: I have and error not when I set the option, but when I try to
execute the query: "You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use
near '';   "   This sounds logic because I am disabling this option.

with 1: same error. This is ilogic.

If i see mysql_basic.c function mysql_odbx_set_option the case of multiple
statments is like this:

case ODBX_OPT_MULTI_STATEMENTS:

#ifdef HAVE_MYSQL_NEXT_RESULT
            if( *((int*) value) == ODBX_ENABLE )
            {
                aux->flags |= CLIENT_MULTI_STATEMENTS;
                return ODBX_ERR_SUCCESS;
            }
            if( *((int*) value) == ODBX_DISABLE )
            {
                aux->flags &= ~CLIENT_MULTI_STATEMENTS;
                return ODBX_ERR_SUCCESS;
            }
#endif
            break;

So, it seems thatopenDBX DO something when I send a 1 or a 0, but the query
doesn't work. Should be this a problem of mysql? any idea?



2) postgresql:

with 0:  I have the error ODBX_ERR_OPTWR which message es "Setting option
failed".
with 1 or X > 1: No error. Works fine the query.

If I see pgsql_basic.c, function pgsql_odbx_set_option I see the case of
multiple statements and it is like this:

        case ODBX_OPT_MULTI_STATEMENTS:

            if( *((int*) value) ) { return ODBX_ERR_SUCCESS; }
            break;

So, if it is 1 or any other value distinct from zero, no problem, It does
nothing and return success. But, if there is zero it does a break and then
goes out of the switch and it returns -ODBX_ERR_OPTWR; In fact, an error.

So, my question is, why is like this? The only thing I thought is that
perhaps Postgresql always accept multiple statements and cannot be disable,
so, if I try to do this, I will have an error.

Ahh and the multiple statements works fine in this case.


very thanks in advance.

Mariano

Re: [opendbx] Question!! changes to odbx_result_finish()

[OpenDBX d. l. <lib...@li...>]

Thanks for your answer, Norbert! I think I know how it works now :)


Hernán

-- 
Well I want you to know
Safe passage to the other side
We can provide

Re: [opendbx] Question!! changes to odbx_result_finish()

[OpenDBX d. l. <lib...@li...>]

Hi Hernán

> I have a question about the new features just added to openDBX.
> Before this changes, When you send a query with odbx_query(), yo must call
> odbx_result(), and for every time it returns a value different than 0, you
> have to call odbx_row_fetch() and process every row, and just then, you can
> send a new query, right?

Yes, that's correct.
Instead of testing for 0, you can use ODBX_RES_DONE and ODBX_ROW_DONE which 
makes your code more meaningful to other developers.

> Now, about the changes to odbx_result_finish(), I don't have to fetch all
> rows, but do I still have to call odbx_result() until it returns 0?? or
> just after calling odbx_result_finish() can I send another query?

You have to call odbx_result_finish() on all result sets returned by 
odbx_result() and it can only fetch outstanding rows, not outstandig result 
sets. You still have to call odbx_result() until it returns ODBX_RES_DONE.

On the other side, the C++ Result object is also capable to fetch outstandig 
result sets in its destructor. If you really know that you send only data 
manipulation statements to the server (DELETE for example), you can 
theoretically shorten your code to:

Conn conn( ... );
conn.bind( .... );
conn.create( Stmt::Simple, "DELETE FROM test" ).execute();
conn.unbind();

That doesn't make sense for SELECT-like statements as you would fetch the 
results and their rows for nothing because they would be thrown away.


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

[opendbx] Question!! changes to odbx_result_finish()

[OpenDBX d. l. <lib...@li...>]

Hi you all!

I'm new to this list, my name is Hernán Cassinelli, and I'm working on the
"OpenDBX for Squeak" project with Mariano Martinez and Esteban Lorenzano.

I have a question about the new features just added to openDBX.
Before this changes, When you send a query with odbx_query(), yo must call
odbx_result(), and for every time it returns a value different than 0, you
have to call odbx_row_fetch() and process every row, and just then, you can
send a new query, right?
Now, about the changes to odbx_result_finish(), I don't have to fetch all
rows, but do I still have to call odbx_result() until it returns 0?? or just
after calling odbx_result_finish() can I send another query?

thanks,

Hernán

-- 
Well I want you to know
Safe passage to the other side
We can provide

Re: [opendbx] OpenDBX 1.3.9 released

[OpenDBX d. l. <lib...@li...>]

sorry...I sent the mail to the list but it was for some friends.


On Thu, May 22, 2008 at 11:18 PM, Mariano Martinez Peck <
mar...@gm...> wrote:

> ya les dije varias veces que se suscriban a la lista de openDBX...son unos
> putos!!!!
>
> miren lo que dice el mail ", as a convenience for developers,
> odbx_result_finish() makes sure
> that all rows are fetched"
>
> Ehhhh ¿eso no es justamente el problema que teníamos? ¿o son mis ganas de
> que así lo fuese??
>
> saludos,
>
> mariano
>
> On Thu, May 22, 2008 at 8:07 PM, OpenDBX devel list <
> lib...@li...> wrote:
>
>> Dear OpenDBX users
>>
>> The OpenDBX library is heading towards the next stable series and in this
>> release the focus was mainly on fixing bugs in existing code. As a result,
>> some patches were applied to the sqlite3 and odbc backends to make them
>> work
>> even better.
>>
>> Additionally, as a convenience for developers, odbx_result_finish() makes
>> sure
>> that all rows are fetched and the parameter for Result::getResult() were
>> made
>> optional. The odbx-sql utility was also improved and is now capable of
>> auto-completing all ANSI SQL keywords.
>>
>> Also, man pages for the odbx_lo_*() and odbx_result_finish() functions as
>> well
>> as the odbx-sql application were written.
>>
>>
>> Norbert
>> --
>> OpenPGP public key
>> http://www.linuxnetworks.de/norbert.pubkey.asc
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> libopendbx-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
>> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>>
>>
>

Re: [opendbx] OpenDBX 1.3.9 released

[OpenDBX d. l. <lib...@li...>]

ya les dije varias veces que se suscriban a la lista de openDBX...son unos
putos!!!!

miren lo que dice el mail ", as a convenience for developers,
odbx_result_finish() makes sure
that all rows are fetched"

Ehhhh ¿eso no es justamente el problema que teníamos? ¿o son mis ganas de
que así lo fuese??

saludos,

mariano

On Thu, May 22, 2008 at 8:07 PM, OpenDBX devel list <
lib...@li...> wrote:

> Dear OpenDBX users
>
> The OpenDBX library is heading towards the next stable series and in this
> release the focus was mainly on fixing bugs in existing code. As a result,
> some patches were applied to the sqlite3 and odbc backends to make them
> work
> even better.
>
> Additionally, as a convenience for developers, odbx_result_finish() makes
> sure
> that all rows are fetched and the parameter for Result::getResult() were
> made
> optional. The odbx-sql utility was also improved and is now capable of
> auto-completing all ANSI SQL keywords.
>
> Also, man pages for the odbx_lo_*() and odbx_result_finish() functions as
> well
> as the odbx-sql application were written.
>
>
> Norbert
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX
>
>

[opendbx] OpenDBX 1.3.9 released

[OpenDBX d. l. <lib...@li...>]

Dear OpenDBX users

The OpenDBX library is heading towards the next stable series and in this 
release the focus was mainly on fixing bugs in existing code. As a result, 
some patches were applied to the sqlite3 and odbc backends to make them work 
even better. 

Additionally, as a convenience for developers, odbx_result_finish() makes sure 
that all rows are fetched and the parameter for Result::getResult() were made 
optional. The odbx-sql utility was also improved and is now capable of 
auto-completing all ANSI SQL keywords. 

Also, man pages for the odbx_lo_*() and odbx_result_finish() functions as well 
as the odbx-sql application were written.


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] Problems compiling 1.3.7 in OSX

[OpenDBX d. l. <lib...@li...>]

On Monday 28 April 2008 13:59:14 OpenDBX devel list wrote:
> Thanks, Norbert... that did the trick, everything is working now.

OK, fixed by SVN commit 48.


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] Problems compiling 1.3.7 in OSX

[OpenDBX d. l. <lib...@li...>]

Thanks, Norbert... that did the trick, everything is working now.

Esteban

El 25/04/2008, a las 6:59PM, OpenDBX devel list escribió:

> Hi Esteban
>
>> I'm having problems compiling the last version with OSX, the linker
>> throws "Undefined symbols: _bindtextdomain", this error did not
>> happen in the previous version.
>> Maybe there are some new dependency not default in OSX?
>
> I think there's a check for the ENABLE_NLS macro missing. Could you  
> apply the
> patch attached and try again?
>
> Thanks
>
>
> Norbert
> -- 
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
> <opendbx- 
> gettext.diff>--------------------------------------------------------- 
> ----------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save  
> $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// 
> java.sun.com/javaone_______________________________________________
> libopendbx-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libopendbx-devel
> http://www.linuxnetworks.de/doc/index.php/OpenDBX

"Querer es suscitar las paradojas"
Camus - El mito de Sísifo

[opendbx] OpenDBX 1.2.6 released

[OpenDBX d. l. <lib...@li...>]

Hi all

This is a security release! The default implementation of odbx_escape() didn't 
escape single backslashes which may make the backends providing no own 
implementation vulnerable to SQL injection attacks. 

In addition, bugs in the sqlite3 and oracle backends were fixed.

The new release is avalable at
http://linuxnetworks.de/opendbx/download/opendbx-1.2.6.tar.gz


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc

Re: [opendbx] Problems compiling 1.3.7 in OSX

[OpenDBX d. l. <lib...@li...>]

Hi Esteban

> I'm having problems compiling the last version with OSX, the linker
> throws "Undefined symbols: _bindtextdomain", this error did not
> happen in the previous version.
> Maybe there are some new dependency not default in OSX?

I think there's a check for the ENABLE_NLS macro missing. Could you apply the 
patch attached and try again?

Thanks


Norbert
-- 
OpenPGP public key
http://www.linuxnetworks.de/norbert.pubkey.asc