On Sat, Oct 6, 2012 at 10:07 AM, Adrian Klaver wrote:
> On 10/05/2012 07:00 PM, Phoenix Kiula wrote:
>>
>> On Sat, Oct 6, 2012 at 12:01 AM, Wolf Schwurack wrote:
>>
>>>
>>> You need to have a pgbouner directory in /var/log and have the owner
>>> pgbouncer. This is easy to test try creating a
This process took me a day and a half but I now have files with copy
dumps for last 11 years.
On the fresh server, instead of 'copy from' with 11 files I
cocatenated the files into one.
Then in a transaction, I imported this file into the new database, which has:
Begin
Truncate table
I would do a CHECK (trim(a) <> '')
TRIM() would add some processing time, so I'd include it only if there
was a chance of spaces getting added. From a puritanical point of
view, it is definitely a good idea.
To the original poster, this syntax should work in MySQL as well:
create table myt
On 22/02/07, Shashank Tripathi <[EMAIL PROTECTED]> wrote:
> I would do a CHECK (trim(a) <> '')
TRIM() would add some processing time, so I'd include it only if there
was a chance of spaces getting added. From a puritanical point of
view, it is definitely a good
select something from othertable;
select * from table where table_id in (?, ?, ?, ?, ?, ?, ?, ...)
This is what MySQL's CEO Martin said in an interview on Slashdot. If
we can manage two queries as above through, say, a PHP application,
with each executing in 0.004 seconds, then an optimized sub
It's a valid discussion here (although better on -advocacy), because it helps
me have the right facts to present to clients about whether they should stay
with a legacy database in MySQL vs upgrading to a modern PostgreSQL.
For all its flaws, MySQL is catching on quick and has a very active
com
