COmanage Developers List

[Scott Koranda <>]

> Wow, yeah, that makes no sense.
> 
> Perhaps more fun related to AdoDB?

Perhaps.

It is also again related in some way to caching.

The order I am doing things is

- deploy, which includes setting up the cache directory 
- ./cake database
- ./cake setup

If I do this with MySQL configured as the database and run a
'find' command in the cache directory nothing has changed
after the setup.

If I do this with PostgreSQL configured as the database and
run a 'find' command in the cache directory then I see that a number of
files have been created in the cache after running './cake
database' and './cake setup'.

If I do things in this order

- deploy
- ./cake database
- ./cake setup
- reset the cache

then the problem/issue goes away.

Note that I made sure that the permissions of files in the
cache where not a problem.

So, doing './cake database' and './cake setup' with PostgreSQL
configured causes caching to happen right then, but the cache
is bad. I notice that the cache does not have in it the
cm_users view/table/model. If I reset the cache then cm_users
appears.

I don't know yet if this is a "bug" or "just how things work
so get the order right".

Scott

> 
> What happens if you try again to login before making the change? Or
> if you drop and recreate the DB without making any other changes?
> 
> On 10/11/11 5:36 PM, Scott Koranda wrote:
> >Hi,
> >
> >So if I follow the deployment instructions for using
> >the registry with PostgreSQL and then try to login I get
> >
> >An Internal Error Has Occurred
> >
> >Error: An Internal Error Has Occurred.
> >
> >If I then edit app/config/core.php and change
> >
> >Configure::write('debug', 0);
> >
> >to instead by
> >
> >Configure::write('debug', 2);
> >
> >and then hit "refresh" in my browser it immediately begins to
> >work. If I change back from level 2 to level 0 it continues
> >working.
> >
> >So any attempt to log information about the problem/bug immediately
> >makes the problem/bug go away.
> >
> >I will keep digging in, but any quick ideas?
> >
> >Scott
> >
> >P.S. The exact same set of code is working fine with MySQL
> >
>