Doctrine DBAL
  1. Doctrine DBAL
  2. DBAL-332

Memory option for Sqlite driver does nothing

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 2.2.2, 2.3
    • Fix Version/s: None
    • Component/s: Drivers
    • Security Level: All
    • Labels:
      None
    • Environment:
      PHP Version 5.3.10
      SQLite Library 3.7.9
      Doctrine 2.3.x-dev
      Dbal 2.3.x-dev
      Symfony 2.1 RC2

      Description

      I'm trying to configure a "memory" sqlite database, as described here: http://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/configuration.html#pdo-sqlite

      So here is my configuration (config_test.yml) :

      Unable to find source-code formatter for language: yml. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml
       
      doctrine:
          dbal:
              driver:    pdo_sqlite
              memory:    true
              user:      db_user
              password:  db_pwd
              charset:   UTF8
      

      I'm then running

      ./app/console doctrine:database:create --env=test

      and the result is a "myBdName" db file (the filename contains the quote!!) in my root folder.

      I don't understand why the file http://www.doctrine-project.org/api/dbal/2.3/source-class-Doctrine.DBAL.Schema.SqliteSchemaManager.html#46 is creating a path option with my DB name, if I comment the line 57, everything seems fine (no more file created).

      I have seen some memory related options in the Doctrine test suite so maybe I'm doing it wrong, and in that case that's a documentation issue I can work on.

      Thx,
      Damien

        Activity

        Hide
        Iain Potter added a comment -

        Apologies for resurrecting an old issue but a google search brought me here.

        Show
        Iain Potter added a comment - Apologies for resurrecting an old issue but a google search brought me here.
        Hide
        Iain Potter added a comment -

        Hi guys, this does not work for me either. Same use case.

        Config:

        driver: pdo_sqlite
        memory: true

        Show
        Iain Potter added a comment - Hi guys, this does not work for me either. Same use case. Config: driver: pdo_sqlite memory: true
        Hide
        Benjamin Eberlei added a comment -

        No feedback on potential fix, this issue is either misconfiguration or wrong use of the API. I couldn't reproduce this and it works for me (TM).

        Show
        Benjamin Eberlei added a comment - No feedback on potential fix, this issue is either misconfiguration or wrong use of the API. I couldn't reproduce this and it works for me (TM).
        Hide
        Benjamin Eberlei added a comment -

        Try removing the user/password keys. memory database connection works for me, this seems to be a configuration issue.

        If you want to create an in memory db for testing then you have to create the schema with SchemaTool inside the phpunit tests.

        Show
        Benjamin Eberlei added a comment - Try removing the user/password keys. memory database connection works for me, this seems to be a configuration issue. If you want to create an in memory db for testing then you have to create the schema with SchemaTool inside the phpunit tests.
        Hide
        Damien ALEXANDRE added a comment -

        My example with "app/console" is misleading,
        what I want to do is building a memory SQLite database on the fly and run some code right after it (in a phpunit test).

        The issue here is that there is an option documented (first link) that doesn't work / is not implemented (second link). And a physic file is generated, it should not.

        As your answer seems to be based on the mistaken impression that I wanted to use volatile database in a persistent way, I'm reopening this issue.

        Thanks for your time.
        Damien.

        Show
        Damien ALEXANDRE added a comment - My example with "app/console" is misleading, what I want to do is building a memory SQLite database on the fly and run some code right after it (in a phpunit test). The issue here is that there is an option documented (first link) that doesn't work / is not implemented (second link). And a physic file is generated, it should not. As your answer seems to be based on the mistaken impression that I wanted to use volatile database in a persistent way, I'm reopening this issue. Thanks for your time. Damien.
        Hide
        Benjamin Eberlei added a comment -

        You cannot create an in memory database using Symfonys database:create. The in memory database will be closed when the request ends. So its completly useless this way. You have to recreate it in every request that you want to use it. It is just good for one request.

        Show
        Benjamin Eberlei added a comment - You cannot create an in memory database using Symfonys database:create. The in memory database will be closed when the request ends. So its completly useless this way. You have to recreate it in every request that you want to use it. It is just good for one request.

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Damien ALEXANDRE
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: