Bug or problem in mysql DB - table vicidial_lists

[phil_discount]

Hello guys,

I've found out a problem with mysql db and odbc connection.
when you connect the db using odbc, you allways getting in each row "#DELETED" because the vicidial_lists table has got a BIGINT unique field.

it's a known bug or problem.

now my question, because i need the table...

can i insert a new field like "ID" with autoincrement/integer value as first field in the table?

regards
philip

[phil_discount]

i make some tests.

1. change the "list_id" field from bigint to int
or
2. add a field with a unique/primary key at last and i have to remove unique/primary key in the field "list_id"...

can i do this?

[heinz]

Hi,
I would say you could do try both ways.
Changing BIGINT to INT shouldn't cause too much trouble.

If you add a field at the end shouldn't be a problem either. Don't put in the front though. Removing the primary key from the list_id is dangerous because it can crash the system if you have multiple list_id entries. But you could try it...

Anyway I wouldn't recommend to do it on a productive system.

Thanks,
heinz

[phil_discount]

i've got no choice...i think i try to change from bigint to int.
it's a testsystem but only for one week then we start outbound with vicidial.

thanks!

[mflorell]

We have a lot of clients using ODBC every day with ViciDial systems and have never heard of this problem. What DB are you using?

[phil_discount]

it seem's to work fine with INT instead of BIGINT. i'm using mysql.
standard vicidialnow installation
it's a problem of microsoft access, it doesn't know the type BIGINT
http://bugs.mysql.com/bug.php?id=12389

[williamconley]

so it's not a problem of ODBC ... it's a problem of microsoft ACCESS, the "mini-database" app that some of us DOSheads use.

do you have the ability to use some other software to interface with mysql and "interpret" for ACCESS? (MSSQL? SQLExpress? anything)

do a quick database dump, change to int and let her rip ... you can always put it back. BUT watch the 4294967295 record limit (i don't think you'll hit it TODAY, but given the fact that this system may still be online next year, and you delete old records and add new ... the recordid value may actually get there ... i've got a couple systems that would get there THIS year ...)

[phil_discount]

Thanks,
mysql ist very good, cheap and quick.
only vicidial_list and vicidial_lists are changed
so i will create a security query in front of the import of new addresses...

when the limit is reached i can export the old addresses in a backup and set back the counter to 1

i thinks thats okay or not?