Mailing List Archive

New release of webcal
Hi all,

Just to late you know that a new version of webcal has been released.
See news and instruction on the the wiki:
http://wiki.davical.org/w/DAViCal_Web_Client

--
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
While you recently had your problems on the run, they've regrouped and
are making another attack.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.morphoss.com/pipermail/davical-users/attachments/20100612/9d6db838/attachment-0001.pgp>
-------------- next part --------------
New release of webcal [ In reply to ]
Hi,

> Just to late you know that a new version of webcal has been released.
> See news and instruction on the the wiki:
> http://wiki.davical.org/w/DAViCal_Web_Client

I'm having trouble installing webcal. All the requirements are
fullfilled, but when I get to step 1/4, I have to fill in:

server: localhost
port: 5432
db name: <is this the name of the davical db or a name for a new db?>
pg dba: postgres <this is the owner of all pgsql db's, right?>
pg dba pw: <hidden>
password for user admin: <this has to be the pw used by the davical
admin, right?>

I have tried several times, with different entries, but I all I get is:
* 'db exists' + back-button
* an error saying there is no such db

Between these tries, I have reset my db to the original state (i.e.
removing the db 'webcal', that seems to be generated by the
installscript just fine).

Any thoughts? I'm really looking forward to try out your project!

Vincent
--
Advocatenkantoor Suy, Van Baeveghem & Van Houtte
Brusselsestraat 108
9200 Dendermonde
T +32.52.52.06.05
F +32.52.52.06.46
W http://www.synergylaw.be
New release of webcal [ In reply to ]
On 15-06-10 20:17, Vincent Van Houtte wrote:
>
> I have tried several times, with different entries, but I all I get is:
> * 'db exists' + back-button
> * an error saying there is no such db
Hi Vincent,

I have come across the same problem as you have. It seems there is a
sanity check in the procedure that confirms that the database exists
before the tables are created. However, it stops if the database *does*
exist and it continues if the database does not exist. The name of the
function "createDatabase", which fills a previously created database is
a bit unfortunate in this respect. The patch below fixes the error.

Cheers,
Stefan.


--- utils/pgsql.php~ 2010-06-12 19:17:47.000000000 +0200
+++ utils/pgsql.php 2010-06-16 15:57:28.000000000 +0200
@@ -43,17 +43,17 @@
}
}

function createDatabase($name) {
$sql = "select count(*) as exist from pg_database where
datname=?";
$sth = $this->prepare($sql);
$sth->execute(array($name));
$res = $sth->fetch();
- if ($res['exist'] == 0) {
+ if ($res['exist'] == 1) {
$this->beginTransaction();
include_once 'db_create.postgresql.php';
$db = make_sql_stm();
foreach ($db as $sql) {
$sth->closeCursor();
$sth = $this->prepare($sql);
if (! $sth) {
$this->rollBack();
New release of webcal [ In reply to ]
On Wed, 16 Jun 2010 16:05:59 +0200
Stefan Rijnhart <stefan.rijnhart at milieudefensie.nl> wrote:

>
> I have come across the same problem as you have. It seems there is a
> sanity check in the procedure that confirms that the database exists
> before the tables are created. However, it stops if the database *does*
> exist and it continues if the database does not exist. The name of the
> function "createDatabase", which fills a previously created database is
> a bit unfortunate in this respect. The patch below fixes the error.
>
What god could possible come out of overwriting an existing database?
Should you by insistent run the installer once again you would loose
all user settings!

By this behavior you are at least given the opportunity to bail out and
make a backup of your existing database if this is not the case it is
easily solved with at dropdb and the rerun the installer.

--
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
Q: Who cuts the grass on Walton's Mountain?
A: Lawn Boy.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.morphoss.com/pipermail/davical-users/attachments/20100616/96c94a94/attachment.pgp>
-------------- next part --------------
New release of webcal [ In reply to ]
On 16-06-10 20:50, Michael Rasmussen wrote:
> On Wed, 16 Jun 2010 16:05:59 +0200
> Stefan Rijnhart<stefan.rijnhart at milieudefensie.nl> wrote:
>
>> I have come across the same problem as you have. It seems there is a
>> sanity check in the procedure that confirms that the database exists
>> before the tables are created. However, it stops if the database *does*
>> exist and it continues if the database does not exist. The name of the
>> function "createDatabase", which fills a previously created database is
>> a bit unfortunate in this respect. The patch below fixes the error.
>>
> What god could possible come out of overwriting an existing database?
> Should you by insistent run the installer once again you would loose
> all user settings!

That is a very good point, and not something that I took into account
for this hasty hack.
> By this behavior you are at least given the opportunity to bail out and
> make a backup of your existing database if this is not the case it is
> easily solved with at dropdb and the rerun the installer.
Our problem was, that this behaviour did not allow us to install the
application at all. It would create the database and the database user
and stop at "Database exist", offering only a back button.

Cheers,
Stefan.