NPCSPAWN command ..broken?

[John Adams]

I am not sure changing the varchar(30) to varchar(50) should effect performance (or it shouldn't really). I'd also guess the Emu doesn't really care what the name of the group is for anything important. spawngroup.name is supposed to only be a friendly name field, yes? The only place I really see it used is during the insert. I thought everything went off the spawngroupid?

But you could be onto something with truncating the name, and attempting to insert duplicate spawngroup.name data. Cuz "name" is Unique.

[cavedude]

Originally Posted by John Adams

But you could be onto something with truncating the name, and attempting to insert duplicate spawngroup.name data. Cuz "name" is Unique.

I just encountered this same thing yesterday. The spawngroup wouldn't create because the spawngroup name was too long so identical names could not be created, only the first worked. Shortening the NPC's name, creating my groups, then changing it back worked perfectly.

Changing the column is a viable solution and it won't cause issues from a technical standpoint. But, that begs do the question do you really want names that long? Heh.

[gernblan]

Originally Posted by John Adams

I am not sure changing the varchar(30) to varchar(50) should effect performance (or it shouldn't really). I'd also guess the Emu doesn't really care what the name of the group is for anything important. spawngroup.name is supposed to only be a friendly name field, yes? The only place I really see it used is during the insert. I thought everything went off the spawngroupid?

But you could be onto something with truncating the name, and attempting to insert duplicate spawngroup.name data. Cuz "name" is Unique.

Well yes but if the insert fails because of the field length, it doesn't get in at all.

Thus, the mobs not showing up later.

So the emu may not care in practice what the name is when reading it... but it sure does care when creating the record in the first place.

Hence changing it to varchar(50).

It does solve thr problem.

And no I do not want the names that long, but what else can I do without adding a bunch of extra (tedious) steps?

[cavedude]

Originally Posted by gernblan

Well yes but if the insert fails because of the field length, it doesn't get in at all.

Thus, the mobs not showing up later.

So the emu may not care in practice what the name is when reading it... but it sure does care when creating the record in the first place.

Hence changing it to varchar(50).

It does solve thr problem.

And no I do not want the names that long, but what else can I do without adding a bunch of extra (tedious) steps?

Agreed, I'm changing this column on PEQ.

[John Adams]

Right, the emu is the one generating the hideously long names, not us. Maybe that random name generator needs a review? But the easy solution is to widen the field.

Thanks Cavedude. PEQdb is still my life blood.

[gernblan]

Glad to help