Results 1 to 3 of 3

Thread: Config.db not getting compiled when created at deplloyment

  1. #1
    Lianja MVP
    Join Date
    Feb 2012
    Location
    Berea, KY, USA
    Posts
    1,965

    Config.db not getting compiled when created at deplloyment

    `As the title says: I changed config.db (in ...\cloudserver\tenants\public\conf). The .dbo was still the old one after having run.

    So I deleted the .do. It still didn't get recompiled.

    So I moved over the .db and .do from dev. The runtime appears to have cached the old .db settings, as debug.txt is reporting an error that was produced (in dev, also, before the change) even though the new .db and .do are there.

    So: two issues:

    1) should not the .db be compiled dynamically at runtime (given that settings can be deployment specific)?

    2) Is the config.do cached? And if so, how would one flush the cache? I have searched for other .db and .do files, and there are none.

    thanks,

    Hank

  2. #2
    Lianja Support Team lianjasupport's Avatar
    Join Date
    Feb 2012
    Location
    Boston USA, Wokingham UK
    Posts
    1,268
    Hi Hank

    Please ticket it. This was affected by the changes made to prevent compilation at runtime.

  3. #3
    Lianja MVP
    Join Date
    Feb 2012
    Location
    Berea, KY, USA
    Posts
    1,965
    Hi,

    I though that might be the case.

    Removing the .db and the .do stopping the old .do from throwing an error when the program loaded. That's a good thing.

    thanks,

    Hank
    Last edited by HankFay; 2014-10-07 at 12:03.

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Journey into the Cloud
Join us