[Firebird-devel] Firebird 2.5.2 RC1 - Trace API - Rock solid
Hello, just letting you know, that the Trace API in 2.5.2 RC1 is rock solid so far. I'm having a test app simulating 150 client connections inserting into a GTT and 7 parallel trace sessions in FB TraceManager with all trace configuration options enabled capturing these events. No single server crash due to the Trace API so far. While this is not an ultimate test covering all possible aspects of the Trace API, it's a good sign compared to 2.5.1. Well done and thanks for your efforts in that area! Regards, Thomas -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Calculated field - is this expected behavior?
Before the discussion is put in the freezer, I think the actual behavior is not consistent. If ALTERing the field formula allow me to reference fields positioned after the calculated one, the extracted metadata should work too. If it is too much difficult to fix this behavior, I would suggest to make the ALTER fail too, to avoid bad surprises when metadata is extracted and run, bringing more consistency between the two operations. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br AP On 09/15/12 21:22, Adriano dos Santos Fernandes wrote: On 15-09-2012 14:02, Carlos H. Cantu wrote: Example: create table a ( field1 computed by (field2 * 0.5), field2 numeric (9,2) ); returns: Column does not belong to referenced table. Dynamic SQL Error. SQL error code = -206. Column unknown. FIELD2. At line 2, column 22. BUT create table a ( field2 numeric (9,2), field1 computed by (field2 * 0.5) ); Works fine. Ideally (but DDL and ideally has a great distance) it should work. I consider that all DDL validations should be done as After this command is executed, will the database state be valid? AP Mentioned trick might be done using gdef. But one had to explicitly AP provide order of fields in relation, something like: AP define relation AP TRANSMSGS AP FAC_CODEposition AP 2, AP NUMBER position AP 3, AP CODE computed by (fac_code * 1 + number)position 1; AP I do not suggest to add explicit position to DDL - just curious. And yes AP - it will be nice to fix DDL to make it perform validations after all AP command is parsed, not for each field. AP -- AP Live Security Virtual Conference AP Exclusive live event will cover all the ways today's security and AP threat landscape has changed and how IT managers can respond. Discussions AP will include endpoint security, mobile security and the latest in malware AP threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ AP Firebird-Devel mailing list, web interface at AP https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Calculated field - is this expected behavior?
On 17/09/2012 10:09, Carlos H. Cantu wrote: Before the discussion is put in the freezer, I think the actual behavior is not consistent. If ALTERing the field formula allow me to reference fields positioned after the calculated one, the extracted metadata should work too. If it is too much difficult to fix this behavior, I would suggest to make the ALTER fail too, to avoid bad surprises when metadata is extracted and run, bringing more consistency between the two operations. Please file a ticket. I believe a fix for 3.0 is not too difficult. Adriano -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] [FB-Tracker] Created: (CORE-3926) Inconsistent behavior with COMPUTED BY fields and metadata extraction
Inconsistent behavior with COMPUTED BY fields and metadata extraction - Key: CORE-3926 URL: http://tracker.firebirdsql.org/browse/CORE-3926 Project: Firebird Core Issue Type: Improvement Components: Engine Affects Versions: 2.1.5, 2.0.7, 2.5.1, 2.1.4, 2.5.0, 2.0.6, 3.0 Initial, 2.1.3, 2.1.2, 2.0.5, 2.1.1, 2.1.0, 2.5.2, 2.5.3, 2.1.6, 3.0.0 Reporter: Carlos H. Cantu Priority: Trivial ALTER statement allows me to change a computed by field with a new formula referencing a field that is positioned higher than the computed by field, but when you extract the table metadata and try to run it, it crashes with Column unknown. error. To reproduce: Step 1) create table a ( field2 numeric (9,2), field1 computed by (field2 * 0.5)); Step 2) alter table a add field3 numeric (9,2); Step 3) alter table a alter field1 computed by (field3 * 0.5); -- This works fine!!! Step 3 works fine, but when you extract the DDL of the table and try to run it, it will crash, since it will be extracted like: CREATE TABLE A ( FIELD2 NUMERIC(9,2), FIELD1 COMPUTED BY (field3 * 0.5), FIELD3 NUMERIC(9,2) ); This means that you may have a good database, but when you extract its metadata into a script to create another empty database, it will crash :-( IMHO, the behavior should be consistent in the two scenarios so, or the table creation should succeed, or the ALTER should had failed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
