You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(25) |
Jun
|
Jul
(8) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(21) |
Feb
(7) |
Mar
(5) |
Apr
|
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
(12) |
Dec
(20) |
2003 |
Jan
(24) |
Feb
(21) |
Mar
(14) |
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
|
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(1) |
2004 |
Jan
(2) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(9) |
Jun
|
Jul
(8) |
Aug
|
Sep
(6) |
Oct
|
Nov
(2) |
Dec
(2) |
2005 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2006 |
Jan
(10) |
Feb
|
Mar
(5) |
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(6) |
Dec
(11) |
2007 |
Jan
(3) |
Feb
(9) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(8) |
Oct
(16) |
Nov
(5) |
Dec
|
2008 |
Jan
(2) |
Feb
(4) |
Mar
(6) |
Apr
(5) |
May
(8) |
Jun
(15) |
Jul
(1) |
Aug
|
Sep
(5) |
Oct
(59) |
Nov
(7) |
Dec
(1) |
2009 |
Jan
|
Feb
(2) |
Mar
(11) |
Apr
(3) |
May
(16) |
Jun
(16) |
Jul
(2) |
Aug
(4) |
Sep
(2) |
Oct
(5) |
Nov
(86) |
Dec
(17) |
2010 |
Jan
(18) |
Feb
(1) |
Mar
(7) |
Apr
(7) |
May
|
Jun
|
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(11) |
Nov
|
Dec
|
2011 |
Jan
(1) |
Feb
|
Mar
(35) |
Apr
(16) |
May
(10) |
Jun
(53) |
Jul
(2) |
Aug
|
Sep
(3) |
Oct
(4) |
Nov
(13) |
Dec
(3) |
2012 |
Jan
(9) |
Feb
|
Mar
(11) |
Apr
(6) |
May
|
Jun
|
Jul
(6) |
Aug
(8) |
Sep
(3) |
Oct
(3) |
Nov
(1) |
Dec
(8) |
2013 |
Jan
(4) |
Feb
(3) |
Mar
(10) |
Apr
(3) |
May
(8) |
Jun
(3) |
Jul
(4) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
(6) |
2014 |
Jan
(6) |
Feb
(9) |
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(5) |
Nov
(4) |
Dec
(4) |
2015 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(9) |
May
(4) |
Jun
(11) |
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
(7) |
Feb
|
Mar
(6) |
Apr
(2) |
May
(11) |
Jun
(2) |
Jul
|
Aug
(33) |
Sep
(3) |
Oct
|
Nov
(4) |
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
(3) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(8) |
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(2) |
2018 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(3) |
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2020 |
Jan
|
Feb
(2) |
Mar
(10) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2021 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
(11) |
Nov
(19) |
Dec
|
From: Alexey K. <ak...@ib...> - 2012-01-09 15:00:36
|
Jiri, During migration we have added 200 most popular redirects for links from old web site. We can do the same for documentation, but who will maintain links after new docs release? It should be constant process to keep links and redirects up to date, and I doubt that web development team can do it, because it's not in our scope. Regards, Alexey > On Sun, Jan 8, 2012 at 10:41 AM, Alexey Kovyazin<ak...@ib...> wrote: >> Documentation is generated from DocBook, in the way which preserve >> cross-links, and then the whole set of htmls are placed to the web-site. >> I suppose it's up to documentation team to create persistent links. > The current content will be kept as is. Only (dynamic) redirects will be added. > >> Personally I think it's not possible to get rid of versioning - there >> always will be outdated docs for old versions of Firebird and tools. > Sure. I'm not saying to remove it. Just to have stable links. > |
From: Jiri C. <di...@ci...> - 2012-01-09 09:17:30
|
On Sun, Jan 8, 2012 at 10:41 AM, Alexey Kovyazin <ak...@ib...> wrote: > Documentation is generated from DocBook, in the way which preserve > cross-links, and then the whole set of htmls are placed to the web-site. > I suppose it's up to documentation team to create persistent links. The current content will be kept as is. Only (dynamic) redirects will be added. > Personally I think it's not possible to get rid of versioning - there > always will be outdated docs for old versions of Firebird and tools. Sure. I'm not saying to remove it. Just to have stable links. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com |
From: marius a. p. <ma...@gm...> - 2012-01-08 19:12:24
|
Please replace jquery 1.3.1 with 1.7.x http://docs.jquery.com/Downloading_jQuery There are many bug fixes also performance improvements http://blog.jquery.com/2011/11/03/jquery-1-7-released/ http://blog.jquery.com/2011/11/21/jquery-1-7-1-released/ |
From: marius a. p. <ma...@gm...> - 2012-01-08 15:11:17
|
At the bottom of the site This site and the pages contained within are Copyright © 2000-2011, Firebird |
From: Alexey K. <ak...@ib...> - 2012-01-08 10:05:12
|
Hello, Documentation is generated from DocBook, in the way which preserve cross-links, and then the whole set of htmls are placed to the web-site. I suppose it's up to documentation team to create persistent links. Personally I think it's not possible to get rid of versioning - there always will be outdated docs for old versions of Firebird and tools. Regards, Alexey > Hi *, > > I'd like to propose to create stable links for documentation topics. > I.e. for EXECUTE STATEMENT currently we have > http://www.firebirdsql.org/file/documentation/reference_manuals/reference_material/html/langrefupd25-psql-execstat.html > . But with post-2.5 this will be obsolete for i.e. links in forums > pointing not to a specific version but to topic itself. > > It would be nice to have, i.e. > http://www.firebirdsql.org/language-reference/execute-statement that > would either redirect (HTTP 302) to latest version or (maybe better) > provider content from latest version and somewhere around bottom > provide links to particular versions. > > The we could remove language reference files from search engines > indexing, because now the traffic and ranks are split between > different version and I think majority of people is only looking to > latest version [1], and index only these stable links. > > [1] Either it's a new user => he is probably using latest FB version. > Or (s)he is experienced user checking out syntax etc., no problem with > versions or (s)he is able to click somewhere around bottom to get > exact version version. > |
From: Jiri C. <di...@ci...> - 2012-01-08 09:34:27
|
Hi *, I'd like to propose to create stable links for documentation topics. I.e. for EXECUTE STATEMENT currently we have http://www.firebirdsql.org/file/documentation/reference_manuals/reference_material/html/langrefupd25-psql-execstat.html . But with post-2.5 this will be obsolete for i.e. links in forums pointing not to a specific version but to topic itself. It would be nice to have, i.e. http://www.firebirdsql.org/language-reference/execute-statement that would either redirect (HTTP 302) to latest version or (maybe better) provider content from latest version and somewhere around bottom provide links to particular versions. The we could remove language reference files from search engines indexing, because now the traffic and ranks are split between different version and I think majority of people is only looking to latest version [1], and index only these stable links. [1] Either it's a new user => he is probably using latest FB version. Or (s)he is experienced user checking out syntax etc., no problem with versions or (s)he is able to click somewhere around bottom to get exact version version. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com |
From: marius a. p. <ma...@gm...> - 2012-01-07 13:05:10
|
Can i send the pages after i finish and my guess they will be included in the main site For example http://www.firebirdsql.org/ro/about-firebird/ I work locally on firebirdsql.ro and when i finish i will send the text , page by page to this list |
From: Olga P. <ole...@dq...> - 2011-12-08 21:14:36
|
Thanx. Done (for flamerobin too). On Wed, Nov 23, 2011 at 10:26 PM, marius adrian popa <ma...@gm...>wrote: > can someone add a notice and announce the new archive list and nntp news > > http://www.firebirdnews.org/?p=6460 > > http://dir.gmane.org/gmane.comp.db.firebird.user > is the archive for firebird-support > > also for flamerobin we do have a archive for mailing lists on sf.net > also on nabble > http://sourceforge.net/mailarchive/forum.php?forum_name=flamerobin-devel > http://flamerobin.2305948.n4.nabble.com/ > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Firebird-website mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-website > |
From: Alexey K. (JIRA) <tr...@fi...> - 2011-12-06 16:30:44
|
[ http://tracker.firebirdsql.org/browse/WEB-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kovyazin updated WEB-60: ------------------------------- Assignee: Olga Popcova (was: Pavel Cisar) > Atkins server is down for a long time (dead?) - change to gmane > --------------------------------------------------------------- > > Key: WEB-60 > URL: http://tracker.firebirdsql.org/browse/WEB-60 > Project: Web site > Issue Type: Bug > Reporter: Carlos H. Cantu > Assignee: Olga Popcova > > In page http://www.firebirdtest.com/en/mailing-lists/ there are several links to atkins server, but the server seems to be down for months. > I suggest stopping using atkins, and replicate all the lists to newsgroups using gmane.org -- 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 |
From: marius a. p. <ma...@gm...> - 2011-12-05 15:29:52
|
The url is here http://dir.gmane.org/gmane.comp.db.firebird.devel and it can be used in your prefered news reader (NNTP protocol is supported also) |
From: Alexey K. <ak...@ib...> - 2011-11-23 21:14:48
|
Hello Marius, Please put request for necessary adjustment to tracker.firebirdsql.org, Web section Regards, Alexey Kovyazin > can someone add a notice and announce the new archive list and nntp news > > http://www.firebirdnews.org/?p=6460 > > http://dir.gmane.org/gmane.comp.db.firebird.user > is the archive for firebird-support > > also for flamerobin we do have a archive for mailing lists on sf.net > also on nabble > http://sourceforge.net/mailarchive/forum.php?forum_name=flamerobin-devel > http://flamerobin.2305948.n4.nabble.com/ > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Firebird-website mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-website > |
From: marius a. p. <ma...@gm...> - 2011-11-23 20:26:16
|
can someone add a notice and announce the new archive list and nntp news http://www.firebirdnews.org/?p=6460 http://dir.gmane.org/gmane.comp.db.firebird.user is the archive for firebird-support also for flamerobin we do have a archive for mailing lists on sf.net also on nabble http://sourceforge.net/mailarchive/forum.php?forum_name=flamerobin-devel http://flamerobin.2305948.n4.nabble.com/ |
From: Lester C. <le...@ls...> - 2011-11-11 11:25:27
|
Alexey Kovyazin wrote: > In 1920 it looks pretty bad, with a lot of unreasonable blank spaces: > http://ge.tt/8nhaCq9?c > > Creating scaled design which will look great from 1024 to 1920 is > non-trivial work. Agreeded ... it's taken weeks to get the framework stable across most browsers and there are still some holes, but now at least I CAN work on upgrading the content. ( The original welcome page has moved inside ;) ) That is until they move the pigging goalposts again! > I think that mobile version (phones) should be completeley different, > but pads already have 1024 or 1280 pixels. I think as long as the normal pages play nicely with smartphones that is all that is needed for now. As long as I can grab a file while out on site with no land based internet access ... yes it does happen more often than one might think ... but I can now at least hook up the laptop to the phone! I can't even access the management console on 1&1 so HAD to get that option working. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php |
From: Dmitry Y. <fir...@ya...> - 2011-11-11 11:12:46
|
11.11.2011 12:51, Alexey Kovyazin wrote: > > Looking at the new site, I often have impression what current width > (1024 pixels) is too small for modern screens (which are at least 1368 > in netbooks and 1920 for desktop systems). Impressions are good, but what exactly is it going to fix / improve? With the fixed sidebars it would allow either bigger fonts or the decreased height (less scrolling) of the contents area. The fonts are already big enough, IMHO. So let's count how many pages overflow two or three screens in height. And then let's estimate wouldn't it be easier / cheaper to split them into two pages instead? Speaking personally, I'd rather keep the current width. Dmitry |
From: Alexey K. <ak...@ib...> - 2011-11-11 10:36:30
|
>BTW, it just make sense to spend resources with mobile site if there is demand for it. Alexey, based on GA stats, what is the percent of visitors using mobile devices? Looking at numbers - we don't need mobile version :) Internet Explorer / Windows 35.07% Firefox / Windows 31.24% Chrome / Windows 20.09% Opera / Windows 6.74% Firefox / Linux 2.38% Safari / Macintosh 1.06% Chrome / Linux 0.86% Chrome / Macintosh 0.44% Firefox / Macintosh 0.44% Safari / Windows 0.28% IE with Chrome Frame / Windows 0.21% Opera / Linux 0.18% Android Browser / Android 0.16% Safari / iPad 0.14% Safari / iPhone 0.13% SeaMonkey / Windows 0.12% Safari / Linux 0.07% Mozilla / Linux 0.05% Opera Mini / (not set) 0.03% Lunascape / Windows 0.03% Safari / iPod 0.02% Mozilla / Windows 0.02% SeaMonkey / Linux 0.02% Mozilla Compatible Agent / iPhone 0.02% Opera / Macintosh 0.02% RockMelt / Windows 0.02% Konqueror / Linux 0.02% Mozilla Compatible Agent / (not set) 0.01% Mozilla Compatible Agent / iPad 0.01% Opera Mini / Android 0.01% Mozilla Compatible Agent / Macintosh 0.01% Firefox / FreeBSD 0.01% Internet Explorer / (not set) 0.01% Safari / (not set) 0.01% (not set) / (not set) 0.01% Mozilla Compatible Agent / Linux 0.01% Opera / (not set) 0.01% Opera / Android 0.01% Regards, Alexey Kovyazin |
From: Carlos H. C. <li...@wa...> - 2011-11-11 10:27:51
|
LC> Norman Dunbar wrote: LC> I must say that I'm in agreement on that! Yes we need to cater for viewing on LC> lower resolution devices, such as the range of smartphone and pads being used LC> nowadays (and serving an alternative theme might help there), ... My opinion is that mobile sites should be completely independent pages, ie: m.firebirdsql.org BTW, it just make sense to spend resources with mobile site if there is demand for it. Alexey, based on GA stats, what is the percent of visitors using mobile devices? []s Carlos H. Cantu www.FireBase.com.br - www.firebirdnews.org www.warmboot.com.br - blog.firebase.com.br |
From: Helen B. <he...@ii...> - 2011-11-11 10:24:16
|
At 11:02 PM 11/11/2011, Alexey Kovyazin wrote: >I see that 17% of visitors use eqipment with 1024 pixels, other 80% has larger screens. > >1024x768 0.178249372 >1280x1024 0.14178184 >1366x768 0.13923542 >1280x800 0.098544102 >1920x1080 0.076243073 >1440x900 0.072257576 >1680x1050 0.065856485 >1600x900 0.037672993 >1920x1200 0.025964135 >1360x768 0.021913225 > > >Having in mind that new site will be (optimistically) in the middle of 2012, I suppose %% of users with 1024 pixels will be less than 10%. Don't count on that. At the rate sales of tablets are going, the numbers are more likely to trend the other way. Also, most people I've had contact with who have laptops with larger screens want to get rid of them because they are so heavy to haul around. And please don't discount us people with imperfect eyesight. It aint broke, so there's nothing to fix, imho. Helen |
From: Martijn T. <m.t...@up...> - 2011-11-11 10:23:05
|
>> Looking at the new site, I often have impression what current width >> (1024 pixels) is too small for modern screens (which are at least 1368 >> in netbooks and 1920 for desktop systems). > While this may be true, bear in mind that not everyone has 'modern' > equipment. I'm working on a laptop that has a maximum resolution of > 1,024 by 768. Instead of 1 wide screen, I have to monitors, 1280 px each. With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! |
From: Alexey K. <ak...@ib...> - 2011-11-11 10:22:19
|
Lester, >Should we move to 1280px in the next version of the site? >> I would say no. And ask the question, why are we using pixels instead of >> percentages? > I must say that I'm in agreement on that! Yes we need to cater for viewing on > lower resolution devices, such as the range of smartphone and pads being used > nowadays (and serving an alternative theme might help there), but leaving 50% of > the screen blank on the current range of desktop machines is a right pain. It > took me a while to get http://medw.co.uk working reasonably well and it still > needs a bit more fine tuning, but I think it scales quite well from 1024 to 1920 > and on most browsers it will handle 800 even ... In 1920 it looks pretty bad, with a lot of unreasonable blank spaces: http://ge.tt/8nhaCq9?c Creating scaled design which will look great from 1024 to 1920 is non-trivial work. I think that mobile version (phones) should be completeley different, but pads already have 1024 or 1280 pixels. Regards, Alexey Kovyazin |
From: Lester C. <le...@ls...> - 2011-11-11 10:11:41
|
Norman Dunbar wrote: >> Should we move to 1280px in the next version of the site? > I would say no. And ask the question, why are we using pixels instead of > percentages? I must say that I'm in agreement on that! Yes we need to cater for viewing on lower resolution devices, such as the range of smartphone and pads being used nowadays (and serving an alternative theme might help there), but leaving 50% of the screen blank on the current range of desktop machines is a right pain. It took me a while to get http://medw.co.uk working reasonably well and it still needs a bit more fine tuning, but I think it scales quite well from 1024 to 1920 and on most browsers it will handle 800 even ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php |
From: Alexey K. <ak...@ib...> - 2011-11-11 10:03:18
|
Hello Norman, >> Looking at the new site, I often have impression what current width >> (1024 pixels) is too small for modern screens (which are at least 1368 >> in netbooks and 1920 for desktop systems). > While this may be true, bear in mind that not everyone has 'modern' > equipment. I'm working on a laptop that has a maximum resolution of > 1,024 by 768. I see that 17% of visitors use eqipment with 1024 pixels, other 80% has larger screens. 1024x768 0.178249372 1280x1024 0.14178184 1366x768 0.13923542 1280x800 0.098544102 1920x1080 0.076243073 1440x900 0.072257576 1680x1050 0.065856485 1600x900 0.037672993 1920x1200 0.025964135 1360x768 0.021913225 Having in mind that new site will be (optimistically) in the middle of 2012, I suppose %% of users with 1024 pixels will be less than 10%. > >> Should we move to 1280px in the next version of the site? > I would say no. And ask the question, why are we using pixels instead of > percentages? Do you mean scaled design? It's very hard to implement reasonable scaled design and, more important, standard in our industry (databases and dev tools) is to have fixed width sites. Personally I like scaled designs - here is my favorite sciteific site, for example http://elementy.ru/, but we are limited in resources to create such design. > >> It will give ability to put 1:1 screenshots, may be we can switch to >> higher types sizes. > Why nor do what Wordpress does, display the image as a thumbnail (of > varying sizes) and click to display full size. Sure, it can be done. > >> I'm looking forward to hear your thoughts. > Hopefully, the above is helpful? Yes, a bit :) Regards, Alexey Kovyazin |
From: Norman D. <No...@du...> - 2011-11-11 09:36:17
|
Morning Alexey, > Looking at the new site, I often have impression what current width > (1024 pixels) is too small for modern screens (which are at least 1368 > in netbooks and 1920 for desktop systems). While this may be true, bear in mind that not everyone has 'modern' equipment. I'm working on a laptop that has a maximum resolution of 1,024 by 768. > Should we move to 1280px in the next version of the site? I would say no. And ask the question, why are we using pixels instead of percentages? > It will give ability to put 1:1 screenshots, may be we can switch to > higher types sizes. Why nor do what Wordpress does, display the image as a thumbnail (of varying sizes) and click to display full size. > I'm looking forward to hear your thoughts. Hopefully, the above is helpful? Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767 |
From: Alexey K. <ak...@ib...> - 2011-11-11 09:15:09
|
Hello All, Looking at the new site, I often have impression what current width (1024 pixels) is too small for modern screens (which are at least 1368 in netbooks and 1920 for desktop systems). Should we move to 1280px in the next version of the site? It will give ability to put 1:1 screenshots, may be we can switch to higher types sizes. I'm looking forward to hear your thoughts. Regards, Alexey Kovyazin |
From: Dmitry (JIRA) <tr...@fi...> - 2011-10-24 07:52:50
|
old transition guides are to be updated for FB2.1/SQL-2008 MERGE statement -------------------------------------------------------------------------- Key: WEB-89 URL: http://tracker.firebirdsql.org/browse/WEB-89 Project: Web site Issue Type: Improvement Environment: FB 2.1+ Reporter: Dmitry Assignee: Alexey Kovyazin SQL 2008 MERGE statement was introduced in FB 2.1 Yet when googling about cross-tables UPDATE statement, it is not shown in results. Old 2003-2005 articles pops up instead, such as http://www.firebirdsql.org/pdfmanual/MSSQL-to-Firebird-Russian.pdf http://www.firebirdsql.org/manual/ru/migration-mssql-syntax-ru.html The latter link, when opened directly from Google does not carry versions disclaimer and does not suggest developer to search for new versions features. I think the paragraphs mentioning MS SQL extended UPDATE table1 FROM table2 statement should be extended with mentioning MERGE statement in FB 2.1 http://firebirdsql.su/doku.php?id=merge http://www.mssqltips.com/sqlservertip/1704/using-merge-in-sql-server-to-insert-update-and-delete-at-the-same-time/ http://en.wikipedia.org/wiki/Merge_(SQL) The whole guide rewriting seems low priority task, that probably would never be done completely. But this particular problem is too easy to find in Google and i think can be fixed in advance to other obsolete things in those article instances. -- 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 |
From: Dmitry (JIRA) <tr...@fi...> - 2011-10-21 16:48:52
|
FB download page: describe obtaining MS VC runtime before installing FB ----------------------------------------------------------------------- Key: WEB-88 URL: http://tracker.firebirdsql.org/browse/WEB-88 Project: Web site Issue Type: Improvement Reporter: Dmitry Assignee: Alexey Kovyazin FB download pages can tell few words about Microsoft Visual C++ runtime libraries, required for corresponding FB version: * which files are required * which VC++ versions they correspond to * how their lack manifests on installation/running of FB * were to download them from, if missed For the story see http://tracker.firebirdsql.org/browse/CORE-3641 -- 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 |