firebird-fr-support Mailing List for Firebird en français (Page 5)
Brought to you by:
makowski
Menu
▾
▴
firebird-fr-support — support en franšais sur Firebird
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(1) |
Apr
(14) |
May
(33) |
Jun
(48) |
Jul
(20) |
Aug
(15) |
Sep
(10) |
Oct
(22) |
Nov
(3) |
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(10) |
Feb
(5) |
Mar
(5) |
Apr
(7) |
May
(12) |
Jun
(11) |
Jul
(2) |
Aug
(6) |
Sep
(10) |
Oct
|
Nov
(3) |
Dec
|
| 2007 |
Jan
(6) |
Feb
(5) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(16) |
Nov
(8) |
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Didier p. b. <dbo...@wa...> - 2006-02-23 16:23:02
|
Bonjour, je souhaiterais savoir comment me connecter depuis delphi =E0 une base = FireBird : Dois-t-on utiliser les composants IBX qui ne seraient plus compatibles = pour des versions > 1.5 ou dois-t-on utiliser les composdants BDE (peu recommandables = apparemment) via un alias utilisant le drivers ODBC Firebird ? (Dans ce = cas je n'ai apparemment pas acces aux "g=E9n=E9rateurs" pas plus qu'aux = domaines notions sp=E9cifiques d'interbase. |
|
From: <Ray...@cl...> - 2006-01-25 20:36:31
|
Oui, j'aimerais bien y assister. Je n'ai pas les comp=E9tences pour = pr=E9parer une sesssion. Salutations,=20 Raymond Cl=E9roux=20 -----Message d'origine----- De : fir...@li... = [mailto:fir...@li...] De la part de = Philippe Makowski Envoy=E9 : 20 janvier 2006 12:31 =C0 : RaymondCleroux Objet : [Firebird-fr-support] Sondage Juste un petit sondage vite fait, si une conf=E9rence Firebird avait lieu en France en 2006, vous y = viendriez ? vous proposeriez de faire une session ? en anglais ? en fran=E7ais ? -- 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 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that = makes searching your log files as easy as surfing the web. DOWNLOAD = SPLUNK! http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 _______________________________________________ Firebird-fr-support mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-fr-support |
|
From: Philippe M. <mak...@fi...> - 2006-01-24 15:29:52
|
Il est l=E0 ! bon je sais c'est pas la 2, mais bon c'est d=E9j=E0 =E7a cf <http://sourceforge.net/project/showfiles.php?group_id=3D9028> --=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: <au...@ho...> - 2006-01-23 14:15:20
|
en tant qu etudiant mes reponses serait non non et du cou ni anglais ni français >From: Philippe Makowski <mak...@fi...> >Reply-To: fir...@li... >To: fir...@li... >Subject: [Firebird-fr-support] Sondage >Date: Fri, 20 Jan 2006 18:20:51 +0100 > >Juste un petit sondage vite fait, >si une conférence Firebird avait lieu en France en 2006, >vous y viendriez ? >vous proposeriez de faire une session ? >en anglais ? >en français ? > >-- >Philippe Makowski > >Firebird serveur SQL open-source en français http://firebird-fr.eu.org > >Ma clé PGP : http://makowski.eu.org/pgpkey.html > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log >files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 >_______________________________________________ >Firebird-fr-support mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-fr-support _________________________________________________________________ 2 Go de stockage avec MSN Hotmail Plus ! http://join2.msn.com/?pgmarket=fr-fr&page=hotmail/es2&DI=81&XAPID=3940&SU=&HL=hpleftslot |
|
From: Philippe M. <mak...@fi...> - 2006-01-23 10:49:01
|
Le 23/01/2006 09:12, Mischler Denis a dit : > Non, car je ne d=E9veloppe pas. certes, mais il n'y a pas que les d=E9veloppeurs qui peuvent assister =E0 une conf=E9rence sur Firebird les administrateurs de base peuvent aussi y trouver leur compte --=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: Mischler D. <den...@th...> - 2006-01-23 08:23:08
|
Non, car je ne d=E9veloppe pas. -----Original Message----- From: fir...@li... = [mailto:fir...@li...] On Behalf Of = Philippe Makowski Sent: vendredi 20 janvier 2006 18:21 To: fir...@li... Subject: [Firebird-fr-support] Sondage Juste un petit sondage vite fait, si une conf=E9rence Firebird avait lieu en France en 2006, vous y viendriez ? vous proposeriez de faire une session ? en anglais ? en fran=E7ais ? --=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 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 _______________________________________________ Firebird-fr-support mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-fr-support |
|
From: <de...@te...> - 2006-01-21 23:13:38
|
Philippe Makowski a =E9crit : >Juste un petit sondage vite fait, >si une conf=E9rence Firebird avait lieu en France en 2006, >vous y viendriez ? > =20 > =E7a d=E9penderait des th=E8mes abord=E9s >vous proposeriez de faire une session ? >en anglais ? >en fran=E7ais ? > > =20 > je pense pas non |
|
From: Richard <ri...@ro...> - 2006-01-20 17:26:17
|
'soir ! j'y viendrais si en fran=E7ais, je ne pense pas pouvoir faire de conference= . RM On 1/20/06, Philippe Makowski <mak...@fi...> wrote: > > Juste un petit sondage vite fait, > si une conf=E9rence Firebird avait lieu en France en 2006, > vous y viendriez ? > vous proposeriez de faire une session ? > en anglais ? > en fran=E7ais ? > > -- > 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 > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Firebird-fr-support mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-fr-support > -- http://www.rootsaka.com |
|
From: Philippe M. <mak...@fi...> - 2006-01-20 17:21:04
|
Juste un petit sondage vite fait, si une conf=E9rence Firebird avait lieu en France en 2006, vous y viendriez ? vous proposeriez de faire une session ? en anglais ? en fran=E7ais ? --=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...> - 2006-01-17 19:25:08
|
Le 17/01/2006 17:56, Nicolas Heurtevin a dit : > Bonjour, >=20 > je souhaiterais connaitre la syntaxe pour renommer une table en SQL > sous FireBird, j'ai essay=E9 celle-ci mais sans succ=E8s : >=20 > RENAME TABLE F_DOCENTETE TO F_DOCENTETE_HST >=20 > Il ne connait pas le mot cl=E9 RENAME >=20 deux solutions : 1/ modifier les tables syst=E8mes (pas recommand=E9 surtout si la table e= n question est li=E9e =E0 d'autres objets) 2/ Cr=E9er une nouvelle table, copier les donn=E9es dans la nouvelle tabl= e, supprimer l'ancienne table exemple : CREATE TABLE USERS2 ( USER_NAME USER_NAME, SYS_USER_NAME USER_NAME, GROUP_NAME USER_NAME, UID UID, GID GID, PASSWD PASSWD, PRIVILEGE PRIVILEGE, COMMENT COMMENT, FIRST_NAME NAME_PART, MIDDLE_NAME NAME_PART, LAST_NAME NAME_PART); INSERT INTO USERS2 (USER_NAME, SYS_USER_NAME, GROUP_NAME, UID, GID, PASSWD, PRIVILEGE, COMMENT, FIRST_NAME, MIDDLE_NAME, LAST_NAME) SELECT USER_NAME, SYS_USER_NAME, GROUP_NAME, UID, GID, PASSWD, PRIVILEGE, COMMENT, FIRST_NAME, MIDDLE_NAME, LAST_NAME FROM USERS; COMMIT; DROP TABLE USERS; COMMIT; --=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: Nicolas H. <nic...@ya...> - 2006-01-17 16:57:53
|
Bonjour, je souhaiterais connaitre la syntaxe pour renommer une table en SQL sous FireBird, j'ai essayé celle-ci mais sans succès : RENAME TABLE F_DOCENTETE TO F_DOCENTETE_HST Il ne connait pas le mot clé RENAME Merci d'avance pour votre aide ;-) Nicolas Nicolas HEURTEVIN 18, rue des Maraîchers 75020 PARIS Tél. : 08 70 30 86 71 Mobile : 06 72 14 67 96 Mail : nic...@ya... Site : http://nicolasheurtevin.free.fr --------------------------------- Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.Téléchargez la version beta. |
|
From: Philippe M. <mak...@fi...> - 2005-12-18 12:22:28
|
Ajout dans la documentation du guide d=92utilisation de nbackup, l=92outi= l de sauvegardes incr=E9mentales de Firebird. Voir en ligne : <http://firebird-fr.eu.org/manuel/nbackup-fr.html> --=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-12-09 20:48:04
|
Bonjour =E0 tous, Firebird 1.5.3 arrive Firebird 2 aussi et les traductions des notes de version aussi Il se trouve que la mani=E8re de travailler a compl=E8tement chang=E9e po= ur une meilleure organisation. Pour organiser le travail, je propose d'abord =E0 chacun de s'inscrire =E0 la liste suivante : <http://lists.sourceforge.net/lists/listinfo/firebird-fr-traduction> Ensuite, je posterai le mode d'emploi et sur la liste et sur le blog de Firebird 2 <http://firebird-fr.eu.org/blob/> dans la cat=E9gorie Traducti= on Les notes de version ont =E9t=E9 transform=E9es en document xml docbook e= t seront donc plus maniable que les documents word. Nous n'avons donc pas =E0 nous soucier de la mise en page, mais seulement du texte. Merci de me faire connaitre votre int=E9r=EAt pour ce travail en vous inscrivant =E0 la liste. <http://lists.sourceforge.net/lists/listinfo/firebird-fr-traduction> --=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-12-09 17:23:13
|
bonjour Le 09/12/2005 16:57, zineb cmoi a dit : > je veux d=E9buter la programmation avec firebird. mais, j'ai un grand > probleme. > sous linux, firebird ne d=E9marre pas, j'ai tjs ce message: > "error while loading shared librairies : libstdc++.so.5: cannot open > shared object file :No such file or directory" > je voudrais que vous me guidiez pour que je puisse demarrer firebird > sous mandriva 2006. > et merci >=20 rien de bien m=E9chant, il suffit d'installer le rpm libstdc++5 dans Mandriva 2006 cela doit =EAtre libstdc++5-3.3.6-2.mdk.rpm par curiosit=E9, tu as install=E9 Firebird =E0 l'aide de quel t=E9l=E9cha= rgement ? parce que le rpm Mandriva aurait du g=E9rer cette d=E9pendance dans contrib il existe firebird-1.5.2.4731-0.3.mdk.rpm --=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: zineb c. <cmo...@ho...> - 2005-12-09 15:58:12
|
bonjour je veux débuter la programmation avec firebird. mais, j'ai un grand probleme. sous linux, firebird ne démarre pas, j'ai tjs ce message: "error while loading shared librairies : libstdc++.so.5: cannot open shared object file :No such file or directory" je voudrais que vous me guidiez pour que je puisse demarrer firebird sous mandriva 2006. et merci _________________________________________________________________ MSN Hotmail : antivirus et antispam intégrés http://www.msn.fr/newhotmail/Default.asp?Ath=f |
|
From: Philippe M. <mak...@fi...> - 2005-12-02 14:23:54
|
Bonjour, Le Vendredi 2 D=E9cembre 2005 15:05, CAMPOS Fabien a =E9crit=A0: > Hello, > > It is possible to know or trace the SQL request received by FireBird (in > real time)? > oui, il y a plusieurs outils permettant cela : UIB SQL Monitor http://www.progdigy.com/ =46BHook http://sourceforge.net/projects/fbutils Planalyzer http://delphi.weblogs.com/IBPLANalyzer=20 =2D-=20 Philippe Makowski =46irebird 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-12-01 13:32:35
|
Le 01/12/2005 14:00, Nicolas Heurtevin a dit : > Bonjour, >=20 > J'utilise depuis bient=F4t 2 mois les bases FireBird via un fichier > gdb, et ce fichier cro=EEt en volume avec le temps sans jamais > d=E9cro=EEtre si des tables de la base sont vid=E9es. Existe-t-il une > possibilit=E9 de compactage comme sous Access ? >=20 Il n'y a pas lieu de s'inqui=E9ter l'espace vide sera r=E9occup=E9. sinon la solution est de faire une sauvegarde restauration de la base mais de toute fa=E7on elle regrossira au fur et =E0 mesure des Insert, ne maigrira pas =E0 la suite de delete, mais les insert suivants utiliseront la place laiss=E9e vide. --=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: Nicolas H. <nic...@ya...> - 2005-12-01 13:01:13
|
Bonjour, J'utilise depuis bientôt 2 mois les bases FireBird via un fichier gdb, et ce fichier croît en volume avec le temps sans jamais décroître si des tables de la base sont vidées. Existe-t-il une possibilité de compactage comme sous Access ? Merci Nicolas Nicolas HEURTEVIN 18, rue des Maraîchers 75020 PARIS Tél. : 08 70 30 86 71 Mobile : 06 72 14 67 96 Mail : nic...@ya... Site : http://nicolasheurtevin.free.fr --------------------------------- Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez le ici ! |
|
From: Philippe M. <mak...@fi...> - 2005-11-18 17:24:34
|
Le 18/11/2005 15:46, Nicolas Heurtevin a dit : > Bonjour, > =20 > J'ai cette erreur lorsque je fais un test de connexion dans les sourc= es de donn=E9es ODBC. > =20 > "operating system directive CreateFile failed" > l'op=E9ration demand=E9e n'a pu s'accomplir sur un fichier ayant une = section mapp=E9e utilisateur ouverte" > =20 > Quelqu'un pourrait m'expliquer de quoi il en retourne ou comment fair= e pour avoir le message Connexion successful! habituel ? > =20 je ne sais pas bien, je ne connais pas bien odbc mais quelle chaine de connexion est utilis=E9e ? la base est sur un lecteur r=E9seau ? (tr=E8s mauvaise id=E9e) --=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: Nicolas H. <nic...@ya...> - 2005-11-18 14:46:58
|
Bonjour, J'ai cette erreur lorsque je fais un test de connexion dans les sources de données ODBC. "operating system directive CreateFile failed" l'opération demandée n'a pu s'accomplir sur un fichier ayant une section mappée utilisateur ouverte" Quelqu'un pourrait m'expliquer de quoi il en retourne ou comment faire pour avoir le message Connexion successful! habituel ? Merci bcp ! Nicolas Nicolas HEURTEVIN 18, rue des Maraîchers 75020 PARIS Tél. : 08 70 30 86 71 Mobile : 06 72 14 67 96 Mail : nic...@ya... Site : http://nicolasheurtevin.free.fr --------------------------------- Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez le ici ! |
|
From: Philippe M. <mak...@fi...> - 2005-11-17 13:48:26
|
Voici le texte original de la conf=E9rence : (je le poste tel quel, mais j'en ferai surement un article en fran=E7ais sur le site firebird-fr.eu.org) pas forc=E9ment une traduction compl=E8te, mais au moins indiquer les poi= nts cl=E9s Firebird Future Development : What to Expect? by Dimitry Yemanov, 2005 1. Review of Firebird 2.0 Some time ago, many of our users were surprised by the number of features released in Firebird 1.5. Honestly, before preparing this paper, I didn't count new features in Firebird 2.0 and I don't have a clue whether it's superior to the version 1.5 in this aspect or not. But, in my opinion, the major benefit of the version 2.0 is not its feature set. "What then?", - you ask. I'd describe Firebird 2.0 as "the version which removes the annoying limits". Sounds not so modest, I know. Let me explain better. No doubt that Firebird has a nice multi-generational architecture and a rich SQL language, an embedded usage and a good performance. But I'm sure almost everyone stepped on some internal limitations that worried or even shocked you. To name a few (in no particular order): * Undocumented table limit of about 35GB, an overflow may cause data corruption * Removing (garbage collecting) nodes from a non-selective index is extremely slow * Bigger page cache often means slower performance * Optimizer is not able to choose a good plan in many cases * International support is weak, a lot of bugs in the Unicode/MBCS handling * Lack of a fast backup/restore mechanism * Weak security and many known vulnerabilities * Requirement of exclusive database access for referential integrity declarations * Too few built-in functions * Unreliable database shutdown Some of them could be of critical priority for your business, others are just annoying. Anyway, I'm glad to report that Firebird 2.0 eliminates most of the aforementioned issues and significantly reduces the impact of others. As for me, this is more important than declaring new language features. But considering also tons of bugfixes and enough new features, Firebird 2.0 definitely represents a major release of your favourite RDBMS. More robust, more feature complete, faster and much more friendly to non-ASCII users. Of course, there are limits that still exist and many features we don't support yet. But we should have some room for future improvements, shouldn't we? We'll talk about the future development a bit later. Well, for those who're interested in numbers, let's read the WhatsNew document or Release Notes and make a summary of total changes per version= : * Version 1.0: 32 improvements, 55 bugfixes * Version 1.5: 58 improvements, 94 bugfixes * Version 2.0: 82 improvements, 140 bugfixes Note: the version 2.0 statistics represents its current state, i.e. Beta 1 release. Impressive, don't you think so? Obviously, Firebird 1.5 was developed longer than Firebird 1.0 and the same appears to be true for Firebird 2.0. But at least you see what the development time is spent for. 2. Roadmap of future versions Speaking about the short-term plans, our primary goal is to merge two codebases (Firebird 2.0 and Vulcan) in order to release Firebird version 3.0. It will be based on the Vulcan tree and will contain its modular architecture and new features, as well as all improvements made in Firebird 2.0. The key features of the Vulcan codebase are: * Globally refactured code * Fine-grained multithreading * Unified provider based architecture * Flexible configuration mechanism * Database level authentication and enhanced security management * Internal DSQL implementation As both Firebird 2.0 and Firebird Vulcan releases are going to co-exist in the next year, you may ask why version 3.0 is numbered as a major release and what else (except of features already done in both codebases) it will contain. A good question. As we want to shorten the 3.0 release cycle as much as possible, no completely new development is expected to happen in that version. But we need to keep our users interested, so something new should be introduced. Solution is simple: the 3.0 release is going to incorporate all the work done inside independent branches. As you perhaps know, there are some improvements done by various Firebird developers that didn't go into the 2.0 release due to time constraints. Some of them are included and being tested in Fyracle, others are still in private trees. Also, we still have a few features in Yaffil that requires backporting into Firebird. Everything mentioned above is exactly the new stuff you'll see in version 3.0. Let's see what has been already done: * Common tables expressions and recursive queries (SQL-99 compliant) Developed by: Paul Ruizendaal Current state: Completed * Global temporary tables (SQL-99 compliant) Developed by: Vlad Horsun Current state: Completed * External procedures / functions (SQL-99 compliant) Developed by: Eugene Putilin, Roman Rokytskyy, Vlad Horsun Current state: Partially done, requires the callback API discussion * New built-in functions (string, math, binary, date/time) Developed by: Oleg Loa Current state: Completed, although requires some changes These features are the major candidates to be included into Firebird 3.0, but there are others (less important) as well. As soon as version 3.0 will be released for public testing, development of the next version will begin. We don't have a decision about version numbering yet, so it could be 3.5 or 4.0 or whatever else. For the duration of this talk, I'll be calling it "version 3.0+", where the plus sign simply means "the next version". Version 3.0+ is going to have major ODS changes as well as a lot of administration, tracing, security, performance and SQL improvements. Most probably, it will also contain an updated remote protocol implementation. Now it's a bit early to say what exactly will be included in that release, but you'll find some hints a bit later. If you'd ask me to outline the generic development priorities, they would be: 1. Reliability and safety (bugfixing, guaranteed recovery, security improvements) 2. Administration and monitoring facilities 3. Compliance with the SQL specification 4. Performance (both algorithmical and optimizer decisions) 5. Language enhancements Now a few words about the 2.0 point releases. First, our usual maintenance schedule will definitely cover the 2.0 product line, so please expect 2.0.1, 2.0.2, etc releases (containing bugfixes) every few months. As always, these point versions will consist of changes backported from the active development branch. So, if you see your "favourite" bug fixed in version 3.0, feel free to ask developers about porting it into the next maintenance release of 2.0.x. Second, I'd expect some of the scheduled 3.0 features (e.g. GTT implementation or WITH [RECURSIVE] code) to be ported into the 2.0 HEAD branch before the merge in order to make a 2.1 minor release possible in the case of noticable delay with the 3.0 development. Recalling everything said above, the timetable should look like: 2005: * Release 2.0 RC and fork the 2.0 HEAD to create the release branch * Port some changes from independent trees to HEAD * Fork the Vulcan HEAD to create the 3.0 development branch 2006, 1st quarter: * Release Firebird 2.0 Final and Firebird Vulcan Final 2006, 2nd quarter: * Release Firebird 3.0 Beta * Fork the 3.0 HEAD to create the 3.0+ development branch 2006, 3rd quarter: * Release Firebird 3.0 Final 2006, 4th quarter: * Release Firebird 3.0+ Beta The key point of this roadmap is when we're able to release Firebird 2.0 and Firebird Vulcan. And this is exactly the point where your help with testing/feedback allows us to move faster. 3. What features to expect? This part of our talk is dedicated to the project activities that we'd expect to see in the not so distant future. To follow the list easily, they're grouped by category, similar to our RFE tracker. Every work has two associated parameters: priority and complexity. The priority value is based on user wishes, it's set up after looking at various polls and forum/newsgroup discussions. In other words, it shows how much our users want a particular feature. Also, this value depends on our analysis of the features offered by our competitors. The complexity value is based on time/effort estimates made by the core team. "None" means that all the required work is already done (in some code branch) and we just need to backport and test it. "Implementation" means that the feature has already been discussed and agreed on, but it still requires some minor discussions and the actual coding. "Design" means that we have a basic agreement and some vision of the things, but the work hasn't been discussed in depth yet and hence we don't have any implementation plan. "Research" means that the work requires serious analysis before discussing its design and implementation specifications. Administration / Tracing / Monitoring * Monitoring via API and/or special tables Perform a "snapshot" monitoring (i.e. at the given moment) of the internal activities inside the engine. Obvious objects of such a monitoring are: databases, attachments, transactions, active requests, resource (memory, CPU) usage, etc. priority =3D high complexity =3D design/implementation * Asynchronous statement cancellation / timeouts Force any of the following actions: cancel a running statement, rollback a transaction, kill an attachment. Allow setting timeouts for SQL statements. Should be available at least at the API level. priority =3D high complexity =3D implementation * Detailed logging/audit Allow to log some events happening on the server. These could be: successful/rejected authentification attempts (containing client host info), prepared/executed SQL statements, committed/rolled back transactions, etc. We need API to set up the required events and to retrieve the audit log. priority =3D medium complexity =3D design * Detailed SQL tracing/profiling Show detailed access path (at the RSB tree level) for every retrieval, count rows (profile CPU time, etc) per every node. Available runtime statistics should be extended. priority =3D medium complexity =3D design/implementation * DDL level and global triggers Allow triggers ON CREATE/ALTER/DROP. Implement triggers attachment and transaction level triggers running in autonomous transactions. priority =3D medium complexity =3D design * PSQL debugging extentions/hooks Allow PSQL debugging via introducing: looper breakpoints, handler callbacks, retrieval of context data, etc. priority =3D low complexity =3D research Security * Embedded users / SQL users management Allow in-database users management. priority =3D high complexity =3D none (done in Vulcan) * User permissions for metadata Protect all metadata with security classes. Implement metadata-level permissions. Add database-level permissions like BACKUP, DROP, etc. priority =3D high complexity =3D design * Pluggable authentication modules Enable using of custom authentication mechanisms (e.g. native OS ones). priority =3D medium complexity =3D design * Security groups Design group-based security as an alternative to the existing role-based one. priority =3D medium complexity =3D research * Database encryption Allow optional encryption of database files. Keys management is an open question here. priority =3D medium complexity =3D research Language extentions * Schemas/namespaces First, it significantly reduces a cost of the issue with short metadata names. Second, it simplifies administration as a number of different databases could be united into a single file. Third, it finally allows us to be fully SQL-92 (entry level) compliant. priority =3D high complexity =3D research * Native long numeric data type Implement long exact numeric data type (with precision longer than 30 decimal digits) and appropriate BCD arithmetics. priority =3D high complexity =3D research * More built-in functions The SQL-99 (or later) ones (those of major importance for us) must be implemented first. Then we need users feedback about other ones. priority =3D high complexity =3D design/implementation * Temporary tables / transient datasets Implement temporary schema objects and/or datasets. SQL-99 compliance is required, extentions are welcome. priority =3D high complexity =3D design/implementation (partially done in Fyracle) * Longer metadata names Up to 128 unicode characters. priority =3D medium complexity =3D design * SQL functions CREATE/ALTER/DROP FUNCTION as per SQL-99. priority =3D medium complexity =3D implementation * Domains everywhere Allow usage of domains in PSQL parameters and variables, as well as in the CAST function. priority =3D medium complexity =3D design * Recursive queries Implement SQL for recursive retrievals. Make it consistent with the SQL specification. priority =3D medium complexity =3D none (done in Fyracle) * Regular expressions Allow usage of regular expressions in search conditions. Add some special syntax (a new predicate) for this purpose. priority =3D medium complexity =3D design/implementation * TEXT BLOB compatible with [VAR]CHAR Allow BLOB SUB_TYPE TEXT to be compatible/interchangable with string data types. Allow text blobs in all built-in functions. priority =3D medium complexity =3D design/implementation * Deferred constraints Implement commit-time constraint checking as per SQL specification. priority =3D low complexity =3D design Performance / Optimizer * Faster outer joins Implement the merge algorithm for outer joins. priority =3D high complexity =3D implementation * Optimizer improvements Fix known bugs/limitations, better optimizer decisions, more data statistics priority =3D medium complexity =3D design/implementation * More access paths Consider implementation of hash join / hash aggregate and other retrieval algorithms used in the competitor RDBMS. priority =3D medium complexity =3D research * More effective sorting Implement partial sorting to spead up FIRST-limited retrievals. Consider sorting recno's instead of entire rows. priority =3D medium complexity =3D design * Optimized network protocol Avoid sending a lot of unneeded data (buffer tails). Consider implementing protocol batches (e.g. prepare + info). Compress spaces more effectively. priority =3D medium complexity =3D research Maintenance / Recovery * Reliable logical backup The only case of unrestorable backup should be a physically corrupted backup. Primitive objects (generators, UDFs, etc) must be restored in the beginning. Computed columns and validation constraints must be restored at the end. The engine should reject inconsistent data instead of transform them when reading (e.g. no value -> NULL). GBAK should allow partial restore, driven by switches or interactively. priority =3D high complexity =3D design * Point-in-time recovery The engine must have an optional ability to maintain a redo log in order to roll it over the last logical backup. No data loss is acceptable= . priority =3D high complexity =3D research Generic / Architecture * SMP support in SS Support effective fine grained multi-threading in the SS architectu= re. priority =3D high complexity =3D none (done in Vulcan) * Compiled statements cache Support caching/reusing of compiled statements. priority =3D high complexity =3D implementation (partially done in Vulcan) * Statement/transaction consistency Solve the known inconsistencies in verbs/transactions. Mostly, this covers blr_for behaviour in INSERT/UPDATE/DELETE statements. Make read-committed transactions compliant with the SQL specification. priority =3D high complexity =3D design * External data sources / database links / cross-database SQL Allow retrievals from external data sources. Provide a few drivers (native FB, JDBC, ODBC) in the distros. Add DDL to declare and DML to use such sources. Implement optimization of retrievals for native data sources. priority =3D high complexity =3D research * External functions/procedures Allow to create procedures/functions written in non-PSQL languages. Provide a few drivers (cdecl, Java, .NET) in the distros. priority =3D high complexity =3D design/implementation (partially done in Fyracle) * Full-text search Implement FTS features inside the engine or add API to plug the external FTS engines in. FB seems to be the only one RDBMS that don't have this feature yet. priority =3D medium complexity =3D research * Clustering MySQL supports clusters (AFAIK, only shared-memory so far), PostgreSQL shared-disk implementation is in the way. More and more buzz about this feature around the world. We should compete. priority =3D medium complexity =3D research * Bi-directional indices Allow reversed index navigation to use ASC-indices for DESC sorting and vice versa. priority =3D medium complexity =3D implementation * Referential integrity without indices Implement (optionally) foreign keys that are not enforced by indices. Also provide an ability to reuse the existing index for a constraint. priority =3D medium complexity =3D design * Bulk load/import Implement effective massive load ability. Provide utility/syntax to use different input formats (csv, xml schema, etc) for import. priority =3D medium complexity =3D design * Bi-directional cursors Consider implementation of scrollable cursors inside the engine or provide a thin layer at the top of the RSB hierarchy to implement the feature via the caching. priority =3D low complexity =3D research * XML integration Provide at least fetch to XML and insert from XML abilities. Consider having BLOB SUB_TYPE XML and implementing XPath queries. priority =3D low complexity =3D research Obviously, the aforementioned list is not complete, it includes only the changes that we consider mostly important. If this list misses your favourite wish, speak now! Now let's create a matrix where most preferrable and easy-to-do features are placed in the top-left corner and most hard-to-implement and/or less wanted ones are in the bottom-right corner. If you'll be moving from one of these corners to another you'll see a most probable feature implementation roadmap. Recalling what has been said before, we could imagine a more detailed roadmap: Firebird 3.0 (the merged version): * Monitoring * Asynchronous statement cancellation * Embedded users / SQL users management * More built-in functions * Temporary tables * SQL functions * Recursive queries * Faster outer joins * SMP support in SS * Compiled statements cache * External functions/procedures As you can see (and as it has been stated earlier), version 3.0 is expected to include the work already done and a few features that are highly wanted and relatively easy to implement. Everything else tends to slow the development down and hence is excluded from the above list. Firebird 3.0+ (the next major version): * Detailed logging/audit * SQL tracing/profilingUser permissions for metadata * Pluggable authentication modules * Security groups * Long exact numeric implementation * Domains everywhere * Regular expressions * TEXT BLOB compatible with [VAR]CHAR * Reliable logical backup * Optimizer improvements * Statement consistency/atomicy, read committed compliance * Optimized network protocol * Bi-directional indices * Referential integrity without indices * Bulk load/import It would also be excellent to design schemas/namespaces and longer metadata names for 3.0+, but no promises here. The same for external data sources and deferred constraints. Firebird 3.0++ (something we don't have a schedule for yet): * PSQL debugging extentions/hooks * Database encryption * More access paths * Full-text search * Clustering * Bi-directional cursors * XML integration Of course, some intermediate or minor releases may happen in the meantime, as we'll try to make the release cycles shorter. As soon as the details are discussed and agreed on among the project admins, you'll see both an actual short-term roadmap and an expected long-term roadmap on our site. --=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: Alexandre B. <ber...@no...> - 2005-10-30 11:37:24
|
Bonjour, J'ai une application client/serveur en java qui travaille sur plusieurs bases Firebird 1.5. Depuis quelques jours, je perds pour des raisons inconnues la connexion =E0 la base. J'arrive tr=E8s bien =E0 r=E9tablir = la connexion mais cela paralyse les utilisateurs Je ne pense pas que cela soit d=FB =E0 mon application car j'ai le = m=EAme probl=E8me avec l'utilitaire Squirrel SQL. Voici les informations sur l'erreur : Code : 335544726 SQL State : HY000 Message : Resource Exception. Error reading data from the connection Que puis-je faire pour r=E9soudre ce probl=E8me ? Merci d'avance pour votre aide Alexandre Berchemin-Sirven |
|
From: Philippe M. <mak...@fi...> - 2005-10-26 17:36:27
|
Le 26/10/2005 17:31, Philippe SCOFFONI a dit : > Bonjour, >=20 > Est-il possible en mode embed d'utiliser un fichier qui serait sur un > r=E9pertoire partag=E9 (sur un serveur de fichier par exemple) ? On a f= ait > l'essai et =E0 pirori cela ne fonctionne pas (blocage =E0 la connexion)= . Je > sais qu'il serait pr=E9f=E9rable de mettre en oeuvre une version serveu= r, > mais cela "complique" l'installation sur des sites distants. Le besoin > est simplement de simplifier aux utilisateurs la sauvegarde de leur > base. Elle est tout de suite sur le serveur, pas de copie ou de > sauvegarde =E0 mettre en place. >=20 ben non ce n'est pas possible par d=E9finition il faut la version normale de Firebird pour cela et franchement installer Firebird, c'est on ne peut plus simple sinon ,la solution c'est de faire un batch ou un utilitaire de sauvegarde =E0 la fermeture de l'appli, comme =E7a pas de souci --=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 S. <phi...@cy...> - 2005-10-26 15:31:31
|
Bonjour, Est-il possible en mode embed d'utiliser un fichier qui serait sur un=20 r=E9pertoire partag=E9 (sur un serveur de fichier par exemple) ? On a fai= t=20 l'essai et =E0 pirori cela ne fonctionne pas (blocage =E0 la connexion). = Je=20 sais qu'il serait pr=E9f=E9rable de mettre en oeuvre une version serveur,= =20 mais cela "complique" l'installation sur des sites distants. Le besoin=20 est simplement de simplifier aux utilisateurs la sauvegarde de leur=20 base. Elle est tout de suite sur le serveur, pas de copie ou de=20 sauvegarde =E0 mettre en place. Merci pour vos r=E9ponses Cordialement Philippe |
|
From: Philippe M. <mak...@fi...> - 2005-10-20 16:11:06
|
Le 20/10/2005 17:53, Camille Leflon a dit : > Merci pour votre r=E9ponse. > C'est bien ce que je craignais ! >=20 > Je suis all=E9 voir la page que vous m'avez donn=E9 qui est tr=E8s int=E9= ressante. > J'ai retenu une bonne id=E9e de cet article : recompiler les sources de > firebird pour impl=E9menter un cryptage/d=E9cryptage lors des lectures > =E9critures sur le disque dur. le plus simple c'est de contacter directement l'=E9quipe de dev http://lists.sourceforge.net/lists/listinfo/firebird-devel ils vous donneront de l'aide l'autre solution est de le faire faire par quelqu'un qui maitrise bien les sources et pour =E7a, le plus simple c'est de contacter Ibphoenix envoyez un mail =E0 Paul Beach de ma part (son email est indiqu=E9 sur la page : http://www.ibphoenix.com/main.nfs?a=3Dibphoenix&page=3Dibp_contact= ) --=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 |
1 message has been excluded from this view by a project administrator.
