Altering A Table At Startup

Squiffy

I'm trying to change a table field in MySQL from an Int to a BigInt.

I've put this in the BS->Properties->Advanced but it doesn't seem to alter the table; it stays as an int :

ALTER TABLE <<DOMAIN>>_MYBO MODIFY StartNumber BIGINT;

Tried with explicit reference to the table instead of <<DOMAIN>> (eg BASTESTDOMAINTEST3_MYBO) as well.

If I cut/paste that code directly into mysql client it works fine.

So, questions :

Can I do this, & is this the correct way to do it?
Should I do this? Are there knock on effects?

AIM seems to handle 64bit numbers internally (in the UI) but saves them as ints in the db. Of course I don't know how AIM uses numbers internally elsewhere so it's possible I'm just creating a bit mess 🙂

Squiffy

Reading this post : https://forum.awareim.com/viewtopic.php?f=1&p=38054
and specifically this quote :

...Aware IM will AUTOMATICALLY EXECUTE the scripts once your application is deployed for the first time...

Looks like I misunderstood when the sql initialisation scripts get executed.

Looks like I have to run them manually whilst testing then. Ah well, what's another post-it note amongst all the others 🙂

Still curious to know if I'm creating a problem for myself by changing the table definition from int to bigint. The only issue I can think of would be if internally AIM doesn't always refer to Number attributes as long.

Probably one for support, that.

customaware

David,

I just noticed that you are using Maria DB.

I found incompatibilities between it and my MS-SQL / MySQL development. An app working fine under both of those had reference attributes trashed under Maria. Just makes me wonder if Maria might have big Int problems also.

Spin up a trial using MS-SQL Express and see if it solves your problem?

Squiffy

I will do that to see what happens.

But I'm pretty sure my issue is that AIM stores numbers in ints instead of bigints, and unless I can safely change that by altering the table then I'm going to have to rethink how I do things.

Cheers,

Squiffy

Mark - tried it with a proper MySQL DB and the same thing happens. The tables get created with INTs for numbers.

Support - please could you say whether changing the type in the DB to a BIGINT would have any negative connotations within AIM? By that I mean does AIM always refer to Numbers as long in the core?