Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed: - TLS - when TLS connections is refused, immediate reply instead of waiting for timeout - TCP - when the call is initiated over TCP but the contact advertised is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR) - record_route_preset() parameter size - ruri matching of canceled transactions (see: http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Hi Daniel,
How about this bug: http://openser.org/pipermail/users/2006-January/002862.html I've tried to look at it but the postgres module is totally unfamiliar to me...
JF
On 2/3/06, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact advertised
is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
A thing that would need fixing is how the mysql queries are generated. To avoid issues, the field names in queries should be surrounded by backticks. This is to avoid a query being invalid because a field name that is used matches a mysql keyword.
I have recently experienced this with mysql 5.0 where a number of new keywords were introduced. I have a table that has a field named 'condition'. In mysql 5.0 I can no longer select this by using a query like:
select condition, uri from table where domain = 'test.com';
instead a query like this works:
select `condition`, `uri` from table where `domain` = 'test.com'
The idea is to surround all the field names in the query in backticks, wherever they appear, to avoid any future issues if some fieldname that openser uses will suddenly become a keyword in the next version of mysql.
On Friday 03 February 2006 13:23, Daniel-Constantin Mierla wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact advertised
is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Dan!
Do you know if this is also an issue in postgres and if backticks works also in postgres?
regards klaus
On Fri, February 3, 2006 13:11, Dan Pascu said:
A thing that would need fixing is how the mysql queries are generated. To avoid issues, the field names in queries should be surrounded by backticks. This is to avoid a query being invalid because a field name that is used matches a mysql keyword.
I have recently experienced this with mysql 5.0 where a number of new keywords were introduced. I have a table that has a field named 'condition'. In mysql 5.0 I can no longer select this by using a query like:
select condition, uri from table where domain = 'test.com';
instead a query like this works:
select `condition`, `uri` from table where `domain` = 'test.com'
The idea is to surround all the field names in the query in backticks, wherever they appear, to avoid any future issues if some fieldname that openser uses will suddenly become a keyword in the next version of mysql.
On Friday 03 February 2006 13:23, Daniel-Constantin Mierla wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact advertised
is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
-- Dan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
On Friday 03 February 2006 14:59, Klaus Darilion wrote:
Hi Dan!
Do you know if this is also an issue in postgres and if backticks works also in postgres?
I do not know about postgres. Also I don't know if backticks are a standard SQL feature or just a mysql extension.
Klaus,
Postgres uses single quotes for strings, and double quotes for "names", so, you could do:
select "condition", "uri" from "table" where "domain" = 'test.com';
-g
On Feb 3, 2006, at 6:59 AM, Klaus Darilion wrote:
Hi Dan!
Do you know if this is also an issue in postgres and if backticks works also in postgres?
regards klaus
On Fri, February 3, 2006 13:11, Dan Pascu said:
A thing that would need fixing is how the mysql queries are generated. To avoid issues, the field names in queries should be surrounded by backticks. This is to avoid a query being invalid because a field name that is used matches a mysql keyword.
I have recently experienced this with mysql 5.0 where a number of new keywords were introduced. I have a table that has a field named 'condition'. In mysql 5.0 I can no longer select this by using a query like:
select condition, uri from table where domain = 'test.com';
instead a query like this works:
select `condition`, `uri` from table where `domain` = 'test.com'
The idea is to surround all the field names in the query in backticks, wherever they appear, to avoid any future issues if some fieldname that openser uses will suddenly become a keyword in the next version of mysql.
On Friday 03 February 2006 13:23, Daniel-Constantin Mierla wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact
advertised is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
-- Dan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Greg Fausak wrote:
Klaus,
Postgres uses single quotes for strings, and double quotes for "names", so, you could do:
select "condition", "uri" from "table" where "domain" = 'test.com';
OK. Thanks.
regards klaus
-g
On Feb 3, 2006, at 6:59 AM, Klaus Darilion wrote:
Hi Dan!
Do you know if this is also an issue in postgres and if backticks works also in postgres?
regards klaus
On Fri, February 3, 2006 13:11, Dan Pascu said:
A thing that would need fixing is how the mysql queries are generated. To avoid issues, the field names in queries should be surrounded by backticks. This is to avoid a query being invalid because a field name that is used matches a mysql keyword.
I have recently experienced this with mysql 5.0 where a number of new keywords were introduced. I have a table that has a field named 'condition'. In mysql 5.0 I can no longer select this by using a query like:
select condition, uri from table where domain = 'test.com';
instead a query like this works:
select `condition`, `uri` from table where `domain` = 'test.com'
The idea is to surround all the field names in the query in backticks, wherever they appear, to avoid any future issues if some fieldname that openser uses will suddenly become a keyword in the next version of mysql.
On Friday 03 February 2006 13:23, Daniel-Constantin Mierla wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact advertised
is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
-- Dan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello,
the new release v1.0.1 is scheduled for Monday, February 27. Anybody which wants to build some packages is welcome. Please drop an email with OS and architecture.
Cheers, Daniel
On 02/03/06 13:23, Daniel-Constantin Mierla wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact advertised
is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Daniel-Constantin Mierla wrote:
Hello,
the new release v1.0.1 is scheduled for Monday, February 27. Anybody which wants to build some packages is welcome. Please drop an email with OS and architecture.
I can take care of debian-3.1-x86 again.
klaus
Cheers, Daniel
On 02/03/06 13:23, Daniel-Constantin Mierla wrote:
Hello everybody,
a new package building of CVS branch rel_1_0_0 (release v1.0.0) will take place soon. This comes as an update to release 1.0.0 which will include the fixings occurred since 1.0.0 was released.
We like to collect all issues of v1.0.0 you are aware of, to be fixed before package generation. Next is a list of the issues that should be fixed:
- TLS - when TLS connections is refused, immediate reply instead of
waiting for timeout
- TCP - when the call is initiated over TCP but the contact advertised
is UDP, the BYE from callee is not routed properly (it is tried TCP due to double RR)
- record_route_preset() parameter size
- ruri matching of canceled transactions (see:
http://openser.org/pipermail/users/2006-February/002951.html)
Any feedback is appreciated.
Cheers, Daniel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel