Unless you find some very compelling reason to keep that constraint, it would be very welcome to patch away that misfeature while at it. :)

/ Johan Sundström (achtung xmas!)

Previous text:

2003-12-20 00:51: Subject: Re: SQL

---

thanks. i missed that while reading Sql.pike. that's not very convenient for an engine called sqlite, is it? :)

On Fri, 19 Dec 2003, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:

...

You need to rename it to something else. A database protocol is not allowed to start with the letters "sql", for some reason.

/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)

/ Brevbäraren

Most probably so, but we kind of know the ones with [Ss]ql prefixes to be a non-growing static collection, unlike the *_result classes. :-)

/ Johan Sundström (achtung xmas!)

Previous text:

2003-12-20 14:02: Subject: Re: SQL

---

I think the constraint is there to prevent you from instantating the things in Sql which _aren't_ protocols, which tend to have names starting with "sql":

...

indices(Sql);

(1) Result: ({ /* 15 elements */ "sybase", "msql", "postgres", "sql_result", "mysql", "sql_util", <-- this one "odbc", "sql", <-- this one "Sql", <-- and this one "rsql", "module", <-- the test seems to miss this one tho "postgres_result", "odbc_result", "oracle", "mysql_result" })

...

(Also, the names ending with "_result" are excempt for the same reason.)

/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)