Maximum number of terms

[Simon]

Is there a maximum number of terms I can have in a Glossary? I have
21,222 terms in my glossary, but every time I try and insert a new
term, it simply doesn't go in. The term counter doesn't go up and the
term doesn't appear in my glossary.

Any ideas?

[porkchop]

Hey Simon!
Wow, 21,000 terms? Sheesh, that's the glossary I dream of building -
doubtless a boatload of work went into that project. Would you care to
point us fellow gloss'ers at the URL?

I can point you here where Dmitry explicitly states that disc capacity
is the only limitation:
http://groups.google.com/group/glossword/msg/185361e3837054e5?hl=en&dmode=source

[quote]
1) The maximum number of terms is limited by the amount of a free
space on hard disk drive where database is installed. No other
restrictions.
[end-quote]

Just taking a run at this....ideas off the top of my head.....
are you sure that the db can accept entries? have any of the following
changed:
db_user?
db_pass?
db_host?
Have you recently updated/upgraded mysql?
what else, if anything, in the hosting environment has changed?

If you discover the reason, could you please post to the group so we
can all see the resolution of the issue?

Good Luck!
./porky

[Simon]

HI porky

anyone interested can go to http://www.fastrad.com.br/glossword/index.php.
This is an English-Portuguese translator's glossary but it covers many
areas. One of the great things about Glossword is that I can have the
Add Terms window open while I work and keep feeding terminology in
which can then be accessed by other translators on our teams, or any
translator for that matter. 21,000 terms is a boatload of work yes,
about 15 years' worth of glossary building all together.

Back to the problem at hand.

Nothing has changed as far as the DB is concerned and no upgrades.
However, I just did a test, and I tried to insert the term "Tailrace"
again. No luck. But for whatever reason, I tried it in all lower case,
"tailrace", and it worked! Which is weird because I always cap the
first letter of the terms, and the terms are usually accepted.

So thanks for replying. It is working without capitalization of the
term, so I'll just keep backing up my database regularly and plug
away.

Cheers
Simon

On 24 mar, 09:57, porkchop <co...@clearcutnetworks.com> wrote:
> On Mar 24, 4:37 am, Simon <simon.foa...@gmail.com> wrote:
>
> > Is there a maximum number of terms I can have in a Glossary? I have
> > 21,222 terms in my glossary, but every time I try and insert a new
> > term, it simply doesn't go in. The term counter doesn't go up and the
> > term doesn't appear in my glossary.
>
> > Any ideas?
>
> Hey Simon!
> Wow, 21,000 terms? Sheesh, that's the glossary I dream of building -
> doubtless a boatload of work went into that project. Would you care to
> point us fellow gloss'ers at the URL?
>
> I can point you here where Dmitry explicitly states that disc capacity

> is the only limitation:http://groups.google.com/group/glossword/msg/185361e3837054e5?hl=en&d...

[Colin Raven]

Simon;

That "Tailrace/tailrace issue sounds like the properties of a db field got mangled...somehow.

Suggestion:

install glossword someplace or other (dummy installation)

install phpMyadmin

compare the field properties in each db.

A penny to a pinch of pigeon poop that a subtle difference exists in the terms field. SOMETHING is different, and only a comparative analysis of each db will reveal the nature of it.

As a cautionary note, that possibly being the case, your backups would contain the error. If/When (we're optimists, right?) it's corrected, you should do a fresh backup with a different name to indicate that it's a post-fix backup and not restore anything prior to that date. Sorry...you doubtless already know this, but a reminder never hurts - in my case anyway, since I often overlook the blindingly obvious! haha.

If you make any discoveries and/or resolve the issue, could you please post to the group so we
can all see what happened (and future viewers can search on the workaround/fix/resolution)

Good Luck!
./porky

Necessary PS: 15 years work.......I absolutely salute you. That's effort on an epic scale!

[Simon]

Hi porky

well, I am a translator, not a MYSQL pro, so I will try and do what
you said but it may take a while. Anyway, I also have exports of my
terms, so hopefully that will be useful if I have to reinstall etc.
Would the XML term exports also contain this error, do you think?

Thanks for all your help and tips!

Simon

> > anyone interested can go tohttp://www.fastrad.com.br/glossword/index.php.

[Cori26]

It is NOT completely true that there is not limit to the number of
terms. True, the total may not be limited, but I have several csv
databases that over 1 million terms, and I have even tried breaking
them down to 65,000 terms and glossword will not import it. I have
tried this on my webserver, on the WAMP version, and also on a version
I am running on XAMPP (which I prefer to wamp). I get the following
error. Any suggestions?


Notice: Undefined index: terms in C:\Program Files\xampplite\htdocs
\glossword\inc\a.import.inc.php on line 718

Warning: array_flip() [function.array-flip]: The argument should be an
array in C:\Program Files\xampplite\htdocs\glossword\inc
\a.import.inc.php on line 1199

Notice: Undefined variable: str in C:\Program Files\xampplite\htdocs
\glossword\inc\a.import.inc.php on line 718

Notice: Undefined index: memory_spend in C:\Program Files\xampplite
\htdocs\glossword\inc\a.import.inc.php on line 1567

Notice: Undefined index: int_items_total in C:\Program Files\xampplite
\htdocs\glossword\inc\a.import.inc.php on line 1614

Notice: Undefined index: int_items_total in C:\Program Files\xampplite
\htdocs\glossword\inc\a.import.inc.php on line 1634


Hope someone has some ideas. If not, is there a way to convert a csv
file to the xml file without first uploading it? What about direct
import into MySQL?

[Cori26]

Just to answer my own question, Dmitry answered saying this:

"Please read my comment #2. Issue 33 .

To increase the limit, edit file `/inc/config.inc.php`
and change `$sys['max_lines_csv'] = 10000;` where `10000` is the
current value."

Thanks for the quick reply!