Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiqueries needed to improve performance ! [DNET392] #396

Closed
firebird-automations opened this issue Sep 5, 2011 · 7 comments
Closed

Comments

@firebird-automations
Copy link

Submitted by: Przemyslaw Jenarzewski (jenar)

Please implement multiqueries support for firebird,
so insert/update/select queries could be send as one sql and results will be delivered as one dataset.
It is very important feature to speed up database access (also for bigger applications).

Some other database providers (MS Sql Server,MySQL,PostGreSQL,SQLite,Microsoft SQL CE) are already using this.
We would able to use some optimisations ie with NHibernate and other cases.

Some performance boost ca 25-30% could be done through this feature (see: http://ayende.com/blog/3979/nhibernate-futures).
"select * from a;
select * from b;" could be send as single sql

With inserts/Updates is the same problem, they are send to DB as single sql which is slow. Again, we could send single sql:
"insert into a ....;insert into b ... ;"
or
"update a set...; update b set..."

@firebird-automations
Copy link
Author

Modified by: Przemyslaw Jenarzewski (jenar)

description: Please implementien multiqueries support for firebird,
so insert/update/select queries could be send as one sql and results will be delivered as one dataset.
It is very important feature to speed up database access (also for bigger applications).

Some other database providers (MS Sql Server,MySQL,PostGreSQL,SQLite,Microsoft SQL CE) are already using this.
We would able to use some optimisations ie with NHibernate and other cases.

Some performance boost ca 25-30% could be done through this feature (see: http://ayende.com/blog/3979/nhibernate-futures).

=>

Please implement multiqueries support for firebird,
so insert/update/select queries could be send as one sql and results will be delivered as one dataset.
It is very important feature to speed up database access (also for bigger applications).

Some other database providers (MS Sql Server,MySQL,PostGreSQL,SQLite,Microsoft SQL CE) are already using this.
We would able to use some optimisations ie with NHibernate and other cases.

Some performance boost ca 25-30% could be done through this feature (see: http://ayende.com/blog/3979/nhibernate-futures).

@firebird-automations
Copy link
Author

Modified by: Przemyslaw Jenarzewski (jenar)

description: Please implement multiqueries support for firebird,
so insert/update/select queries could be send as one sql and results will be delivered as one dataset.
It is very important feature to speed up database access (also for bigger applications).

Some other database providers (MS Sql Server,MySQL,PostGreSQL,SQLite,Microsoft SQL CE) are already using this.
We would able to use some optimisations ie with NHibernate and other cases.

Some performance boost ca 25-30% could be done through this feature (see: http://ayende.com/blog/3979/nhibernate-futures).

=>

Please implement multiqueries support for firebird,
so insert/update/select queries could be send as one sql and results will be delivered as one dataset.
It is very important feature to speed up database access (also for bigger applications).

Some other database providers (MS Sql Server,MySQL,PostGreSQL,SQLite,Microsoft SQL CE) are already using this.
We would able to use some optimisations ie with NHibernate and other cases.

Some performance boost ca 25-30% could be done through this feature (see: http://ayende.com/blog/3979/nhibernate-futures).
"select * from a;
select * from b;" could be send as single sql

With inserts/Updates is the same problem, they are send to DB as single sql which is slow. Again, we could send single sql:
"insert into a ....;insert into b ... ;"
or
"update a set...; update b set..."

@firebird-automations
Copy link
Author

Commented by: @cincuranet

This is a limitation of Firebird protocol itself, not the provider.

You can use FbBatchExecution or execute block as workaround.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Author

Commented by: Przemyslaw Jenarzewski (jenar)

First, thank you for quick answer ;)

I mean, we need this functionality, not workaround for it,
so if it is limitation of protocol, then the protocol should be enhanced.

Could you please change this issue to protocol improvement (because i don't know how it internally works, and what kind of "issue" it is) so developers could start work on it ?

We really need this.

@firebird-automations
Copy link
Author

Commented by: Przemyslaw Jenarzewski (jenar)

Or should i create new ticket under "core" for it ?

@firebird-automations
Copy link
Author

Commented by: Przemyslaw Jenarzewski (jenar)

Created new "Core" ticket CORE3592

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants