Re: Firebird doesn't support MSVC 2015

Noel Grandin <noelgrandin -AT- gmail.com>
Wed, 2 Mar 2016 14:12:31 +0200



On 2016/03/02 2:11 PM, Michael Stahl wrote:


personally i'd be inclined towards alternatives that are less likely to
trigger toolchain problems - maybe there's a SQL database implemented
in, say, Java somewhere...


Maybe even one that shares a committer with LO ?

http://h2database.com/html/main.html

Context

Firebird doesn't support MSVC 2015 · David Ostrovsky
- Re: Firebird doesn't support MSVC 2015 · Miklos Vajna
- Re: Firebird doesn't support MSVC 2015 · Michael Stahl
  - Re: Firebird doesn't support MSVC 2015 · Stephan Bergmann
    - Re: Firebird doesn't support MSVC 2015 · Michael Stahl
      - Re: Firebird doesn't support MSVC 2015 · Noel Grandin
        
        Re: Firebird doesn't support MSVC 2015 · Alexander Thurgood
        
        Re: Firebird doesn't support MSVC 2015 · julien2412
        
        Re: Firebird doesn't support MSVC 2015 · Stephan Bergmann
        
        Re: Firebird doesn't support MSVC 2015 · Wols Lists
        
        Re: Firebird doesn't support MSVC 2015 · Jonathan Aquilina
        
        Re: Firebird doesn't support MSVC 2015 · Wols Lists
        
        Re: Firebird doesn't support MSVC 2015 · Andrzej Hunt
        Re: Firebird doesn't support MSVC 2015 · Wols Lists
        
        Firebird/SQLite/H2/HSQLDB etc. -- punted to ESC call, please · Bjoern Michaelsen
- Re: Firebird doesn't support MSVC 2015 · Lionel Elie Mamane

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.