Closed GoogleCodeExporter closed 9 years ago
4. change db in config
in fact, rename it to db-name2 and change in config to db-name2 (for example)
Original comment by ykoro...@gmail.com
on 5 Mar 2013 at 9:33
why do you use such technique $_SESSION[COOKIENAME.'currentDB'] ?
Original comment by ykoro...@gmail.com
on 7 Mar 2013 at 7:16
[deleted comment]
Hmm. I cannot exactly reproduce this. It creates an empty db with the old name
for me - which is also not what should happen.
I will have a look at it.
> why do you use such technique $_SESSION[COOKIENAME.'currentDB'] ?
So is the question "why is COOKIENAME there?"?
Then the answer would be:
You might have multiple php-scripts on your domain that use sessions or even
multiple PLA installations. We prefix our session-variables with COOKIENAME to
make sure we don't get into conflict with session-variables set by other
scripts or PLA installations.
Original comment by crazy4ch...@gmail.com
on 9 Mar 2013 at 1:28
Original comment by crazy4ch...@gmail.com
on 9 Mar 2013 at 1:28
Original comment by crazy4ch...@gmail.com
on 9 Mar 2013 at 1:43
This issue was closed by revision r350.
Original comment by crazy4ch...@gmail.com
on 9 Mar 2013 at 1:45
Original issue reported on code.google.com by
ykoro...@gmail.com
on 5 Mar 2013 at 9:24