AW: SQL generated schema

. I am not aware of problems with mysql at the moment, but I do not know the reason for not having any problems, cause the templates were not changed since then. I will look into it and maybe we'll come back to your offer. Thomas Thoralf Rickert [EMAIL PROTECTED] schrieb am

AW: SQL generated schema

Some template sets for databases do not allow forward declarations on foreign key. So you have to make sure that the referenced table is before the referencing table in the schema.xml Ah, maybe it's not part of this thread but I remember that I had this cross reference problem with Torque

Using multiple joins to a table

Hiho! I've little freaky question. There a two tables: Table #1 (debitor) has following columns: id (primary) address_id (not null, foreign key to address) invoice_address_id (not null, foreign key to address) delivery_address_id (not null, foreign key to address) ... Table #2

Solution for Log4j error

Hi all! I'm not on this list, but I think, you are or someone who's looking for an answer is interested in solving the log4j error in torque-gen und torque. The problem is, that torque and torque-gen report a problem, that there is no log4j appender for org.apache.torque-gen.engine and

Re: [courier-users] Aliases with Courier ESMTP using ESMTPD

In /etc/courier/aliases/users I've added a line like this: @domain2: user@domain1 You're missing a step. What this syntax means is that when a message arrives for [EMAIL PROTECTED] then it will be delivered to [EMAIL PROTECTED] You need to include instructions in the [EMAIL PROTECTED]

Re: [courier-users] 454 TLS not available: missing RSA private key

Polarcom Webmaster schrieb: I receive this error when trying to send message to some.domain.com I have a generated key in .../share/esmtpd.pem So what's the problem? Points TLS_CERTFILE in ...etc/esmtpd to the same absolute location and is esmtpd.pem readable by courier (chmod 400, chown

[courier-users] Aliases with Courier ESMTP using ESMTPD

Hi all! I'm using authmysql to authorize SMTP connections. Mails for users that are in the database will be accepted. Now I tried to send a mail to somebody@domain2 but the system answers 550 User unknown. In /etc/courier/aliases/users I've added a line like this: @domain2: user@domain1

[courier-users] Courier ESMTPD Relaying Problem - need help

Hi all! I've installed the whole Courier Suite on my internet server. It uses authmysql to authorize users. This works fine for IMAP, POP3 and SMTP Authentification. So, it seems, that Courier uses the users and passwords saved in the MySQL database. But I've one small problem: Any mail

Re: [courier-users] Courier ESMTPD Relaying Problem - need help

Add domain and .domain to a file in '/etc/courier/esmtpacceptmailfor.dir'. Argh - I forgot that command :( Okay - THANKS! Now messages are accepted (currently not really delivered, but this is a maildrop problem). bye Thoralf --- This

Re: HTTPClient Feature Patch

Hi! I would recommend against doing it in this way. Primarily because it involves polling (the second thread calling getWrittenRequestBodyBytes() repeatedly) and because of the added synchronization overhead. Yes, I would call it just once a second, but nobody knows what someone else does.

HTTPClient Feature Patch

of transfered bytes. So I can show the user, that the application still works... Do you think, that this small patch is useful for you too or do you know another way? Thanks, Thoralf Rickert - To unsubscribe, e-mail: [EMAIL PROTECTED

HTTPClient Feature Patch

of transfered bytes. So I can show the user, that the application still works... Do you think, that this small patch is useful for you too or do you know another way? Thanks, Thoralf Rickert - To unsubscribe, e-mail: [EMAIL PROTECTED

<    1   2