firebird-fr-tests Mailing List for Firebird en français (Page 2)
Brought to you by:
makowski
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
(3) |
Apr
(4) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(5) |
Sep
(1) |
Oct
(5) |
Nov
(4) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Philippe M. <mak...@fi...> - 2006-04-01 16:05:56
|
http://firebird.sourceforge.net/index.php?op=3Dfiles&id=3Dfb2_rc1 Il y aura une RC2 c'est certain, par contre il ne devrait pas y avoir de RC3 surtout si les tests de cette RC1 sont bien faits, donc n'h=E9sitez pas =E0 remonter les probl=E8mes =E9ventuels Bon tests --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Philippe M. <mak...@fi...> - 2005-11-12 12:10:48
|
<http://firebird-fr.eu.org/blob/index.php?2005/11/12/12-firebird-20-beta1= -est-disponible> --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Philippe M. <mak...@fi...> - 2005-07-20 17:27:25
|
Vous le trouverez ici : http://www.firebirdsql.org/download/prerelease/win32/ Attention, l'ODS a chang=E9 depuis l'Alpha 2 donc vous devez faire un backup restore de vos bases pour les utiliser avec cette nouvelle version= . Les versions Linux arrivent. --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Philippe M. <mak...@fi...> - 2005-05-08 17:58:58
|
-------- Original Message -------- Subject: Firebird 2.0 ALPHA2 field-test Date: Sun, 08 May 2005 17:28:37 +0200 From: Pavel Cisar You have got this letter because you have signed up for managed Firebird 2.0 field testing. The second public alpha release is available for Win32 (including embedded) and Linux (both Classic and SuperServer, but SS NPTL version only). You can download it from http://firebird.sourceforge.net/index.php?op=3Dfiles&id=3Dfb2_alpha02. Please, read carefully the ALPHA2 Release Notes (available at http://firebird.sourceforge.net/download/prerelease/Firebird_v2Alpha02.Re= leaseNotes_0200_20.zip) General Notes ------------- The software in this early distribution of Firebird 2 is an alpha version. Test it till it chokes, but do not put it into production use and do not try it out on any databases that you care about! All new changes and new features are subject to further change and/or withdrawal in subsequent alpha and beta releases, leading up to final release. Do not assume that databases created by or upgraded to the on-disk structure of this alpha will be upwardly compatible with subsequent test builds/releases. Possible pitfalls ----------------- There are some changes in new version that may cause trouble to your existing applications. Those are: 1. DSQL parsing of table aliases is stricter 2. OLD context variables now read-only 3. New Reserved Words & Changes 4. Security Changes in Firebird 2.0 5. New Configuration Parameters and Changes Read the Release Notes for details. Let us know how those changes affected your existing applications. Main targets for ALPHA2 testing ------------------------------- Several critical bugs were found in first round of testing that are fixed in Alpha 2 (complete list is at the end of this letter). If your testing was affected by any such bug, please verify with Alpha 2 that they it's really fixed. Primary goal for this roundup is the same as for Alpha 1 - regression testing. So, if you have an application that runs with Firebird, take it on a "test drive" with this alpha release in some testing environment, preferably with real-world data. Of course, you can pick up any testing method you like, and you can even focus only on a particular area you're most interested in (for example performance, backup/restore, new features, optimizer etc.). Please, refer to Alpha 1 letter for list of areas that were reworked in Fb 2.0. In this round of testing, we would like ask you to test next few features introduced in FB 2.0, that could be easily tested with your applications without much additional work: 1. The 252-byte index length limit is gone. If you ever hit this limit before, try it again. 2. Expression Indexes. If you have queries in your application that may take advantage from them, try them. 3. UDF library diagnostic messages improved. If you have any UDF's in use, you can easily create a crash situation and let us know if this improvement was helpful for you. 4. Bugs Fixed. Take a look at list of fixed bugs. You may find bug(s) that haunted you before are finally fixed. Please, verify that any such issue was really fixed. Secondary targets for ALPHA2 testing ------------------------------------ There are many new features that would need separate manual testing as your applications do not use them. You don't need to test them in this alpha2 release, but it would be nice if you would test at least some of them. 1. CREATE SEQUENCE, NEXT VALUE FOR 2. REVOKE ADMIN OPTION FROM 3. BLOB SUB_TYPE BINARY 4. EXECUTE BLOCK 5. ROWS syntax 6. UNION DISTINCT 7. New DISTINCT equivalence predicate 8. NULL can now be a value for syntactic purposes 9. FIRST/SKIP and ROWS syntaxes and PLAN and ORDER BY clauses can now be used in view specifications. 10. CROSS JOIN implemented 11. Subqueries and INSERT statements can now take union sets 12. Context variable ROW_COUNT returns select count 13. Get context variables via system functions 14. Built-in function IIF() added 15. Built-in function SUBSTRING() enhanced 16. Improvements in user-specified query plans 17. Improved GROUP BY and ORDER BY clauses 18. Explicit cursors in PSQL 19. Defaults for Stored Procedure arguments 20. LEAVE <label> syntax support 21. PSQL stack trace 22. Call a UDF as a void function 23. Users can modify their own passwords 24. ISQL improvements 25. On-line incremental backup 26. External Functions 27. Derived tables 28. NBACKUP How to report back ------------------ We're expecting a report from you that will have the following structure= : 1. Summary. A brief summary of your findings and "feelings" about quality of this particular release. 2. Testing environment. If your testing environment is the same as one described in your last report, you can simply say so and skip the detailed description in your report. Otherwise we would like know next information: Type: local, remote or both Server: HW - CPU(s), HDD(s) size, SMP/HT OS - name, version, service pack Client: HW - CPU(s), HDD(s) size, SMP/HT OS - name, version, service pack FB arch.: CS, SS, EMB Used database(s): Number of files, size, number of tables, SP's, triggers, max. number of rows in single table Creation method: restore under FB2 or created under older version and used under FB2 It would be nice if you would include gstat (use -s and -r options) reports for used databases created before you start testing and after you finished your tests. Application: Short description, you may skip it if you included it in your sign-up message. 3. Tested areas and test outcome(s). Besides usual testing to check that your application(s) works as expected, each field test round has primary and secondary targets for testing. These targets would be listed in a field test letter like this one, and you should describe which target(s) you have actually tested, along with a description of your findings. 4. Issues found. Fill in all issues you have found in the tested release, each in separate section. If you have already filled a Bug tracker entry for any issue, fill in only the entry number here, otherwise give us full details (see "Bug reporting and Support" below for instructions). Bug Reporting and Support ------------------------- The aim of this alpha is to find bugs and "gotchas". Please make a point of reading the instructions for bug-reporting in the article How to Report Bugs Effectively (http://firebird.sourceforge.net/index.php?op=3Ddevel&sub=3Dqa&id=3Dbugre= port_howto), at the Firebird Project website (NOTE for translators: there are also translated versions). Follow these guidelines as you test this software: 1. Write detailed bug reports, supplying the exact server model and build number of your Firebird kit. Also provide details of the OS platform. Include reproducible test data in your report and post it to our Field Test Tracker (http://sourceforge.net/tracker/?atid=3D593943&group_id=3D9028&func=3Dbro= wse). Don't post reports to the main Bug Tracker, which is for stable releases ONLY. 2. If you want to start a discussion thread about a bug or an implementation, do so by subscribing and posting to the Testers' list (mailto:fir...@li...?subject=3Dsubscribe) or directly to the firebird-devel list. 3. Don't use the regular bug-tracker or the firebird-support list to report bugs in the alpha or to ask for expanded details about how a new feature works. 4. DO NOT create bug-tracker entries for installation and documentation issues, but list those in your reports! Bugs fixed in Alpha2 -------------------- Field-test tracker #1188734 WHERE CURRENT OF doesn't work #1173948 Prompt is shown when using -i switch #1173858 FB2 Alpha1: Installation: Windows Link failed #1169884 Navigation vs IS NULL vs compound index #1169764 Server crash on restore (new indices issue) #1169730 Database corruption caused by the new GC code #1169728 FIRST 1 vs ORDER DESC vs explicit plan (ODS11) #1169723 Database that will not restore using FB 2.0 Alpha1 #1169708 select from selectable SP takes MUCH more time than before #1169707 Database corruption - page 0 expected type 5, found 1 #1168910 isql stops when meet any chars in comment #1168898 FB2 - domain with check containing select Bugs Tracker #1191006 Using where params in SUM return incorrect results #750662 Multiple declaration of blob filters #450404 isql uppercases role in the command line #1016969 -804 Data type unknown in UPDATE with CASE and parameters #1155520 Any user can replace databases created by others #1124720 Problem with "FOR EXECUTE STATEMENT ... DO SUSPEND;" HAPPY TESTING ! Pavel Cisar Firebird Project QA Division --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Philippe M. <mak...@fi...> - 2005-05-01 08:35:39
|
Des binaires windows "snapshot" quotidiens disponibles Des binaires contruits chaque jours avec le code de Firebird 2.0 pour Windows sont disponibles. Vous pouvez donc avancer sur vos tests. Pour t=E9l=E9charger : http://www.firebirdsql.org/download/snapshot_builds/win= / --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Evelyne G. <EG...@so...> - 2005-04-19 14:05:33
|
Bonjour, Quand quelqu'un se connecte pour la premi=E8re fois =E0 ma base de = donn=E9es, l'utilisation du fichier d'=E9change augmente de 255 Mo sur = le serveur (c'est proportionnel =E0 la grosseur de la base de = donn=E9es...). Est-ce que quelqu'un d'autre a eu le m=EAme probl=E8me = ?? Ceci fait que je ne peux pas travailler avec Firebird 2 m=EAme pour = les tests car r=E9guli=E8rement, j'obtiens l'erreur que mon fichier de = donn=E9es est dans un espace m=E9moire que je ne peux acc=E9der. Environement de test : Type: local et distant Serveur: Pentium 4 3.20GHz, HDD 149 Go, 512 Mo RAM, Windows XP Pro SP2. Client : M=EAme configuration. FB arch.: SS Base(s) utilis=E9e(s): 5 fichiers pour un total de 3.63 Go, 70 tables Connexion avec fbClient.dll dans IBExpert ou dans Delphi par FIBPlus. Evelyne |
From: Philippe M. <mak...@fi...> - 2005-04-06 06:14:35
|
Voil=E0 les notes de version sont publi=E9es en fran=E7ais il y a encore beaucoup de chemin jusqu' =E0 la sortie finale y compris de ces notes ;) [http://firebird.sourceforge.net/download/prerelease/Firebird_v2Alpha01.R= eleaseNotes_0200_02-fr.zip] En esp=E9rant que cela vous aide dans vos tests --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Philippe M. <mak...@fi...> - 2005-04-05 06:11:58
|
Le 04/04/2005 22:44, Philippe Makowski a dit : > Bonjour, >=20 >=20 > il serait bien que chacun poste dans le tracker juste un d=E9tail, si vous n'avez pas de compte =E0 SourceForge, serait i= l possible d'indiquer votre nom lors de l'=E9tablissement des rapports ? merci, cela rendra le suivi plus facile. sinon utilisez votre login SourceForge. --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Philippe M. <mak...@fi...> - 2005-04-04 20:44:15
|
Bonjour, il serait bien que chacun poste dans le tracker (http://sourceforge.net/tracker/?func=3Dadd&group_id=3D134863&atid=3D7312= 68) ou bien acc=E8s par (http://sourceforge.net/projects/firebird-fr/) au moins la partie description de sa plateforme de test comme d=E9crit ci apr=E8s, merci d'avance car ensuite il faut que je fass= e remonter tout cela =E0 Pavel en anglais : 1. R=E9sum=E9. Un bref r=E9sum=E9 de ce que vous avez trouv=E9 et vos impressions sur la qualit=E9 de cette version sp=E9cifique. 2. Environement de test. Type: local, distant ou les deux Serveur: HW - CPU(s), HDD(s) taille, SMP/HT OS - nom, version, service pack Client: HW - CPU(s), HDD(s) taille, SMP/HT OS - nom, version, service pack FB arch.: CS, SS, EMB Base(s) utilis=E9e(s): Nombre de fichiers, taille, nombre de tables, proc=E9dures stock=E9es, triggers, nombre max. de lignes dans une table M=E9thode de cr=E9ation: restauration sous FB2 ou creation sous une ancie= nne version et utilisation sous FB2 Il serait bien de joindre le r=E9sultat de gstat (utilisez les options -s et -r) pour les bases utilis=E9es avant le d=E9but des tests et apr=E8s v= os tests . Application: Courte description . Vous pouvez vous dispenser de tout cela ensuite dans les rapports futurs si votre environnement de test ne change pas. 3. Tests effectu=E9s et r=E9sultats. Outre le fait de v=E9rifier que votre application fonctionne comme pr=E9v= u, chaque phase de test aura des objectifs principaux et secondaires. Ces objectifs seront d=E9crits dans une lettre comme celle ci, et vous devrez indiquer quels objectifs vous avez test=E9, ainsi que la decription de ce que vous avez d=E9couvert. 4. Probl=E8mes trouv=E9s. Indiquez tous les probl=E8mes que vous avez rencontr=E9, dans des section= s diff=E9rentes. --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |
From: Jean L. <jea...@ph...> - 2005-03-27 08:44:07
|
Jean Lycoops Pharmacien Bansions 33 4845 Sart-lez-Spa Belgique Je d=E9veloppe une application Java avec Eclipse et SWT. C'est une application de gestion de pharmacie qui doit tourner sur Mac=20 OS X et Windows. On en est aux tests pr=E9liminaires en production. On doit piloter des imprimantes tickets, des robots distributeurs, des=20 lecteurs de carte =E0 puce. Le pied en multi-plate-forme ! Pour info : il n'y a, par exemple, pas de port s=E9rie sur les iMac... On travaille sur des r=E9seaux h=E9t=E9rog=E8nes (m=E9lange de Mac et PC) Je suis malheureusement dans l'incapacit=E9 de tester vu qu'il n'y a pas=20 de binaire pour MAC OS X Je ne crois pas qu'il soit envisageable de m=E9langer 1.5 sur PC et 2.0=20 sur mac pour un test s=E9rieux. Seul point positif l'application (PC) tourne sans le moindre probl=E8me e= n 2.0 J'attend =E9galement avec impatience les librairies Java qui permettont=20 d'assurer la maintenance (Backup-restore etc) autrement qu'en effectuant des appels natifs sur GBAK ou autre bricolages foireux. Bonjour =E0 tous les testeurs. Jean |
From: Claude et J. P. <jpc...@ml...> - 2005-03-26 22:06:57
|
jpc...@ml... |
From: Philippe M. <mak...@fi...> - 2005-03-25 13:50:34
|
Bonjour =E0 tous comme vous avez certainement vu, le site web Firebird-fr.eu.org a des probl=E8mes de disponibilit=E9s :( et donc il est en cours de migration. du coup j'en profite pour mieux structurer les choses. J'ai donc ouvert un compte =E0 sourceforge : http://sourceforge.net/projects/firebird-fr/ vous trouverez dans la partie docs et les =E9l=E9ments de communication comme la premi=E8re lettre de pr=E9sentation de la m=E9thode de travail p= our la version Alpha1. d'autre part, il serait bien d'utiliser le Tracker (http://sourceforge.net/tracker/?group_id=3D134863) pour envoyer les r=E9sultats de vos tests, voire m=EAme dans un premier tant une descripti= on telle qu'indiqu=E9 dans la lettre (http://sourceforge.net/docman/display_doc.php?docid=3D27636&group_id=3D1= 34863) de votre plateforme de test sinon, vous pouvez donc utiliser cette liste pour discuter de tout cela et vous pr=E9senter les uns aux autres. merci encore et d=E9sol=E9 de ces changements, mais je pense qu'en fait, = ce sera plus efficace comme cela. --=20 Philippe Makowski Firebird serveur SQL open-source en fran=E7ais http://firebird-fr.eu.org Ma cl=E9 PGP : http://makowski.eu.org/pgpkey.html |