** Official July Chat Thread: The Black Swan **

[Klompy]

[ QUOTE ]
1) Switch database to postgresql.
2) ????
3) Profit.

[/ QUOTE ]

I've tried to do this before, but it never works

[grouchie]

[ QUOTE ]
[ QUOTE ]
1) Switch database to postgresql.
2) ????
3) Profit.

[/ QUOTE ]

I've tried to do this before, but it never works

[/ QUOTE ]

create a new postgre database, export old hands, import into new?

[Cry Me A River]

That's how I did it. It's tedious as hell and takes forever, but it works.

[Klompy]

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
1) Switch database to postgresql.
2) ????
3) Profit.

[/ QUOTE ]

I've tried to do this before, but it never works

[/ QUOTE ]

create a new postgre database, export old hands, import into new?

[/ QUOTE ]

Every time I've tried to convert a database to sql it takes about an entire day and eventually just shuts down. My comp isn't very old either, but I just gave up on it a long time ago. I just make new databases all the time, and I'm ok with it.

[Cry Me A River]

[ QUOTE ]
[ QUOTE ]
Time to compact your database?

[/ QUOTE ]

Even right after compacting, it does that. I just finished an hour long session, and PT had four total imports (one with 220 hands).

But hey, all the hands are there, and I don't actually notice the lag, so it doesn't bother me.

[/ QUOTE ]

How big is your database? If it's Dbase, it's probably almost full.

Check the file size, I think the maximum is around 1gig.

[grouchie]

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
1) Switch database to postgresql.
2) ????
3) Profit.

[/ QUOTE ]

I've tried to do this before, but it never works

[/ QUOTE ]

create a new postgre database, export old hands, import into new?

[/ QUOTE ]

Every time I've tried to convert a database to sql it takes about an entire day and eventually just shuts down. My comp isn't very old either, but I just gave up on it a long time ago. I just make new databases all the time, and I'm ok with it.

[/ QUOTE ]


Do a slower process and give it a few days.

Export all your hands.

When you go to import them into the new postgre database, do it in incriments.

Like 50 files at a time or something.

It will take a good long time, but you'll be happier when you get it done.

[Jurrr]

posgresql is the only reasonable option. That DB rules.

[Klompy]

[ QUOTE ]
posgresql is the only reasonable option. That DB rules.

[/ QUOTE ]

You guys really think it's that big of a difference? How smooth does sql run when you have a really big database? The problem is that If I were to swith right now I think I'd have to start from scratch or close seeing as the last database I started prob only has 20k hands played on it and maybe 60k hands datamined. I currently just have hud linked to a few different databases to have stats on people.

[TheProdigy]

[ QUOTE ]
[ QUOTE ]
posgresql is the only reasonable option. That DB rules.

[/ QUOTE ]

You guys really think it's that big of a difference? How smooth does sql run when you have a really big database? The problem is that If I were to swith right now I think I'd have to start from scratch or close seeing as the last database I started prob only has 20k hands played on it and maybe 60k hands datamined. I currently just have hud linked to a few different databases to have stats on people.

[/ QUOTE ]

If it lags that much with a 60k database, you have external problems.

Regardless, the bigger the DB the more you should consider having it on postgre

[bottomset]

made a 39min 4tabling vid nl10

hopefully it turned out ok