groonga-normalizer-mysql 1.1.0-1 source package in Ubuntu
Changelog
groonga-normalizer-mysql (1.1.0-1) unstable; urgency=medium * Team upload. * New upstream release. -- HAYASHI Kentaro <email address hidden> Fri, 01 Jan 2016 03:13:48 +0900
Upload details
- Uploaded by:
- Groonga Project
- Uploaded to:
- Sid
- Original maintainer:
- Groonga Project
- Architectures:
- any
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Xenial | release | universe | misc |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
groonga-normalizer-mysql_1.1.0-1.dsc | 1.9 KiB | 8ff0b9949a85980c756e7e176060e02f1327242ef094edf5d42e30d95d06c186 |
groonga-normalizer-mysql_1.1.0.orig.tar.gz | 516.8 KiB | 525daffdb999b647ce87328ec2e94c004ab59803b00a71ce1afd0b5dfd167116 |
groonga-normalizer-mysql_1.1.0-1.debian.tar.xz | 3.0 KiB | 35d243dbf802bb8583726d916f4359539e3695625313ba7f6541dce0b1a2489d |
Available diffs
- diff from 1.0.6-1 to 1.1.0-1 (138.4 KiB)
No changes file available.
Binary packages built by this source
- groonga-normalizer-mysql: MySQL derived normalizer for Groonga
Groonga is an open-source fulltext search engine and column store.
It lets you write high-performance applications that requires fulltext
search.
.
This package provides a normalizer which normalizes text as same as
MySQL does.
.
Groonga has its own normalizers by default, but that behavior is a bit
defferent from MySQL does, so as a result, it affects search results.
These normalizers are useful if you regards it important for keeping
normalizer compatibility with MySQL in Mroonga which uses Groonga as
storage engine.
- groonga-normalizer-mysql-dbgsym: debug symbols for package groonga-normalizer-mysql
Groonga is an open-source fulltext search engine and column store.
It lets you write high-performance applications that requires fulltext
search.
.
This package provides a normalizer which normalizes text as same as
MySQL does.
.
Groonga has its own normalizers by default, but that behavior is a bit
defferent from MySQL does, so as a result, it affects search results.
These normalizers are useful if you regards it important for keeping
normalizer compatibility with MySQL in Mroonga which uses Groonga as
storage engine.